Triple
T15693135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paleofarsalos–Kalambaka railway line |
E380383
|
entity |
| Predicate | convertedToStandardGauge |
P120311
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Paleofarsalos–Kalambaka railway line, convertedToStandardGauge, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToStandardGauge Context triple: [Paleofarsalos–Kalambaka railway line, convertedToStandardGauge, yes]
-
A.
gaugeConversionSection
Indicates a section or segment where a change or transition between different measurement or track gauges occurs.
-
B.
upgradedToBroadGauge
Indicates that something previously using a narrower or different railway track gauge has been converted to use broad gauge.
-
C.
originalStandardGaugeOperator
Indicates that an entity served as the initial or primary operator of a railway system using the standard track gauge.
-
D.
gaugeType
Indicates the specific kind or category of gauge associated with an entity or measurement.
-
E.
standardGaugeWidth
Indicates that something has the standard or officially accepted gauge width, typically referring to the distance between two rails in a railway track.
- F. None of above. chosen
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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0b4d01c9c81909f6b611e8144c838 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 10, 2026, 4:44 a.m.