Triple
T19111209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Litochoro railway station |
E467791
|
entity |
| Predicate | hasFootbridgeOrUnderpass |
P25561
|
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: [Litochoro railway station, hasFootbridgeOrUnderpass, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFootbridgeOrUnderpass Context triple: [Litochoro railway station, hasFootbridgeOrUnderpass, yes]
-
A.
hasFootbridge
chosen
Indicates that there exists a footbridge providing a pedestrian connection between the related entities.
-
B.
hasBridgeUnderpasses
Indicates that one structure, typically a bridge, includes or provides underpasses that allow passage beneath it.
-
C.
hasUnderpass
Indicates that one location or structure includes or is connected by an underpass beneath another feature or pathway.
-
D.
hasBridgeOrStructure
Indicates that there exists a bridge or similar structural connection between the related entities.
-
E.
hasFootbridgeOrigin
Indicates that a footbridge originates, starts, or has its starting point at the referenced location or 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e394969c81909d09b2300ea0e041 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:04 p.m.