Triple
T35107789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Südbahn railway line |
E1013199
|
entity |
| Predicate | originalStartPoint |
P389
|
FINISHED |
| Object | Vienna |
E7023
|
NE FINISHED |
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: Vienna | Statement: [Südbahn railway line, originalStartPoint, Vienna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalStartPoint Context triple: [Südbahn railway line, originalStartPoint, Vienna]
-
A.
startPoint
chosen
Indicates the initial location or position from which an object, path, or action begins.
-
B.
startPointState
Indicates the initial state or condition from which a process, event, or transition begins.
-
C.
startPointLocatedIn
Indicates that the starting point of something is geographically or spatially located within a specified area or region.
-
D.
startPointDescription
Indicates the textual description that specifies the initial point or location where something begins.
-
E.
initialPosition
Indicates the original or starting location of an entity before any movement or change in position occurs.
- F. None of above.
Provenance (4 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37cffac58481909a973bf9513a4011 |
completed | June 21, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.