Triple
T27913057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agartala Railway Station |
E705987
|
entity |
| Predicate | openedAsBroadGaugeTerminus |
P178024
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Agartala Railway Station, openedAsBroadGaugeTerminus, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsBroadGaugeTerminus Context triple: [Agartala Railway Station, openedAsBroadGaugeTerminus, 2016]
-
A.
openedAsTerminus
Indicates that a transportation line or route was initially opened with this location serving as its end-point terminus.
-
B.
openedAsRailTerminal
Indicates that a facility or location began operation specifically as a rail terminal when it first opened.
-
C.
openedAsBRT
Indicates that a transit service, corridor, or route was initially launched or began operation specifically as a bus rapid transit (BRT) system.
-
D.
openedAsINDStation
Indicates that a location or facility began operation specifically as a station within the IND (Independent Subway System) network.
-
E.
openedAsCTAStation
Indicates that an entity began operation specifically as a Chicago Transit Authority (CTA) station at the time it opened.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 27, 2026, 6:51 p.m.