Triple
T29444193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pan-European Corridor X |
E746799
|
entity |
| Predicate | railAxisFollows |
P70018
|
FINISHED |
| Object | Salzburg–Ljubljana railway |
—
|
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: Salzburg–Ljubljana railway | Statement: [Pan-European Corridor X, railAxisFollows, Salzburg–Ljubljana railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railAxisFollows Context triple: [Pan-European Corridor X, railAxisFollows, Salzburg–Ljubljana railway]
-
A.
ridgeAxis
Indicates the central line or crest along the top of a ridge that defines its main axis or direction.
-
B.
transportAxis
Indicates a directional path or axis along which something is transported or moved from one location to another.
-
C.
followsRailroad
chosen
Indicates that one entity is aligned with or travels along the path defined by a railroad.
-
D.
roadAxis
Indicates a central reference line that defines the primary longitudinal direction or alignment of a road.
-
E.
railAlignmentType
Indicates the specific geometric or structural configuration in which a rail or track segment is aligned relative to a reference or route.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b1f46cc8190aeed9e77976f5cd1 |
completed | May 2, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:25 p.m.