Triple
T22646862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Central Railway |
E558985
|
entity |
| Predicate | zonalRailwayCode |
P63313
|
FINISHED |
| Object | 05 |
—
|
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: 05 | Statement: [East Central Railway, zonalRailwayCode, 05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zonalRailwayCode Context triple: [East Central Railway, zonalRailwayCode, 05]
-
A.
railwayZoneNumber
chosen
Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
-
B.
hasRailwayZone
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
-
C.
railroadCodeFor
Indicates that a specific railroad code is assigned to or used to identify a particular railroad entity.
-
D.
railwayCodeType
Indicates the specific classification or type category assigned to a railway code within a railway coding system.
-
E.
hasSubwayCode
Indicates that an entity is associated with a specific subway system code used to identify it within that transit network.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f170382ba48190b77692762db43313 |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.