Triple
T35269465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR |
E1018624
|
entity |
| Predicate | railwayZoneCategory |
P178057
|
FINISHED |
| Object | zonal railway of Indian Railways |
—
|
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: zonal railway of Indian Railways | Statement: [SR, railwayZoneCategory, zonal railway of Indian Railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayZoneCategory Context triple: [SR, railwayZoneCategory, zonal railway of Indian Railways]
-
A.
railwayZoneType
chosen
Indicates the classification or category of a railway zone to which a given railway-related entity belongs.
-
B.
hasRailwayZone
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
-
C.
railwayZoneNumber
Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
-
D.
railwayZoneJunction
Indicates a junction where multiple railway zones or lines intersect or connect.
-
E.
formerRailwayZone
Indicates that an entity was previously part of a specified railway administrative zone or system, but is no longer within that zone.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:02 p.m.