Triple
T37915717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reitzenhain–Flöha railway |
E945808
|
entity |
| Predicate | hasTerminusVillage |
P4011
|
FINISHED |
| Object | Reitzenhain |
—
|
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: Reitzenhain | Statement: [Reitzenhain–Flöha railway, hasTerminusVillage, Reitzenhain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminusVillage Context triple: [Reitzenhain–Flöha railway, hasTerminusVillage, Reitzenhain]
-
A.
hasVillage
chosen
Indicates that an entity possesses, contains, or is associated with a village.
-
B.
hasVillageAtExit
Indicates that a village is located at or directly adjacent to an exit (such as a road, highway, or route exit).
-
C.
hasVillageAtHead
Indicates that a village is located at the head (source or upper end) of a geographic feature such as a valley, river, or bay.
-
D.
isVillage
Indicates that the subject entity is classified as a village, typically a small human settlement or community.
-
E.
hasVillageAccess
Indicates that an entity is permitted to enter, use, or benefit from the facilities, services, or areas of a particular village.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 3, 2026, 4:20 p.m.