Triple
T32217907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hengst station |
E822978
|
entity |
| Predicate | lineTerminated |
P46766
|
FINISHED |
| Object | Schneeberg line |
—
|
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: Schneeberg line | Statement: [Hengst station, lineTerminated, Schneeberg line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineTerminated Context triple: [Hengst station, lineTerminated, Schneeberg line]
-
A.
lineTerminatedBeyond
Indicates that a line or linear feature ends at a point located beyond a specified reference boundary or limit.
-
B.
lineTerminusForSomeServices
Indicates that a location serves as the endpoint or terminus for at least some, but not necessarily all, of the services operating on a given line.
-
C.
lineTerminusFor
chosen
Indicates that one entity serves as an endpoint or terminus of a particular line or linear feature represented by another entity.
-
D.
lineTerminusDirection
Indicates the directional orientation or bearing at which a line segment or route terminates at its endpoint.
-
E.
definesLineTerminator
Indicates that one entity specifies what character or sequence of characters marks the end of a line for another entity.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbfc1f8819096f7f4b34573db85 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:38 a.m.