Triple
T26647618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanded railway division |
E668961
|
entity |
| Predicate | railwayZoneAbbreviation |
P24188
|
FINISHED |
| Object | SCR |
—
|
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: SCR | Statement: [Nanded railway division, railwayZoneAbbreviation, SCR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayZoneAbbreviation Context triple: [Nanded railway division, railwayZoneAbbreviation, SCR]
-
A.
railwayZoneNumber
Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
-
B.
railwayZoneHeadquartersFor
Indicates that a location serves as the administrative headquarters for a particular railway zone.
-
C.
hasRailwayZone
chosen
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
-
D.
formerRailwayZone
Indicates that an entity was previously part of a specified railway administrative zone or system, but is no longer within that zone.
-
E.
railwayRegion
Indicates a relationship where a railway or rail network is associated with, located in, or administered within a particular geographic region.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 2:31 a.m.