Triple
T31918512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oirschot |
E814902
|
entity |
| Predicate | hasVillageInMunicipality |
P4011
|
FINISHED |
| Object | Middelbeers |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Middelbeers | Statement: [Oirschot, hasVillageInMunicipality, Middelbeers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVillageInMunicipality Context triple: [Oirschot, hasVillageInMunicipality, Middelbeers]
-
A.
hasVillage
chosen
Indicates that an entity possesses, contains, or is associated with a village.
-
B.
isVillageDistrictOf
Indicates that one administrative unit is a village-level district that belongs to or is governed by a larger territorial entity.
-
C.
hasVillageCommunity
Indicates that an entity possesses, is associated with, or includes a village-level community as part of its structure or domain.
-
D.
hasVillageAtExit
Indicates that a village is located at or directly adjacent to an exit (such as a road, highway, or route exit).
-
E.
isVillage
Indicates that the subject entity is classified as a village, typically a small human settlement or community.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 1, 2026, 12:02 a.m.