Triple
T14163697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secunderabad Junction |
E351012
|
entity |
| Predicate | isMajorRailwayHub |
P1071
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Secunderabad Junction, isMajorRailwayHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorRailwayHub Context triple: [Secunderabad Junction, isMajorRailwayHub, true]
-
A.
hasMajorRailwayStation
chosen
Indicates that a place contains or is served by a principal railway station that functions as a major hub for rail transport.
-
B.
hasMajorRailLinksTo
Indicates that there are significant railway connections or routes between two locations.
-
C.
hasMajorHubIn
Indicates that an entity maintains a primary or significant operational hub or center in a specified location.
-
D.
isTransportCenterOf
Indicates that a location functions as a primary hub or central node for transportation activities serving another area or network.
-
E.
capitalCityIsMajorTransportHub
Indicates that the capital city functions as a primary hub for transportation networks, with significant connectivity and traffic across major transport modes.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de613a4a2081908fd51bf4b4d82b6c |
completed | April 14, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:59 a.m.