Triple
T35358469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mysore State Railway |
E1021402
|
entity |
| Predicate | railwayZoneIntegration |
P24188
|
FINISHED |
| Object | Southern Railway (India) |
—
|
NE NERFINISHED |
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: Southern Railway (India) | Statement: [Mysore State Railway, railwayZoneIntegration, Southern Railway (India)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayZoneIntegration Context triple: [Mysore State Railway, railwayZoneIntegration, Southern Railway (India)]
-
A.
railwayZoneType
Indicates the classification or category of a railway zone to which a given railway-related entity belongs.
-
B.
railwayZoneJunction
Indicates a junction where multiple railway zones or lines intersect or connect.
-
C.
railwayZoneNumber
Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
-
D.
hasRailwayZone
chosen
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
-
E.
railwayZoneFormationRelatedTo
Indicates a relationship where the formation, establishment, or reorganization of a railway zone is connected to a specific factor, event, decision, or entity.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:03 p.m.