Triple
T4738344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Railway zone |
E105178
|
entity |
| Predicate | zoneCode |
P58492
|
FINISHED |
| Object | NR |
—
|
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: NR | Statement: [Northern Railway zone, zoneCode, NR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneCode Context triple: [Northern Railway zone, zoneCode, NR]
-
A.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
-
B.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
-
C.
postalCode
Indicates the numerical or alphanumerical code assigned to a geographic area for mail delivery associated with an entity.
-
D.
areaCode
Indicates that a location, phone number, or region is associated with a specific telephone area code.
-
E.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
- F. None of above. chosen
Provenance (4 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6485d690819098dc4a974516da6b |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd637e19e081909e415544106c7835 |
completed | March 20, 2026, 3:10 p.m. |
Created at: March 20, 2026, 1:19 p.m.