Triple
T17397652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorakhpur Junction railway station |
E422994
|
entity |
| Predicate | platformLength |
P127328
|
FINISHED |
| Object | approximately 1366 meters |
—
|
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: approximately 1366 meters | Statement: [Gorakhpur Junction railway station, platformLength, approximately 1366 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformLength Context triple: [Gorakhpur Junction railway station, platformLength, approximately 1366 meters]
-
A.
platformHeight
Indicates the vertical distance or elevation of a platform relative to a defined reference level.
-
B.
platformModel
Indicates that one entity serves as the underlying platform or foundational model upon which the other entity is built, operates, or depends.
-
C.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
D.
hasPierLength
Indicates that one entity (typically a pier or similar structure) has a specified length measurement.
-
E.
platformPlank
Indicates that one entity serves as a plank or board component of a platform structure associated with another entity.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43abe6f708190944aad636e1eb9a1 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:45 a.m.