Triple
T10761221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Central Railway zone |
E253830
|
entity |
| Predicate | dateOfOperationalization |
P90584
|
FINISHED |
| Object | 2002-10-01 |
—
|
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: 2002-10-01 | Statement: [East Central Railway zone, dateOfOperationalization, 2002-10-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfOperationalization Context triple: [East Central Railway zone, dateOfOperationalization, 2002-10-01]
-
A.
dateImplemented
chosen
Indicates the date on which something (such as a plan, rule, feature, or system) was put into effect or made operational.
-
B.
dataProducedAt
Indicates that specific data is generated, recorded, or created at a particular time or location.
-
C.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
D.
operatedAt
Indicates that an operation, procedure, or activity was performed at a specific location or facility.
-
E.
dateEnacted
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d731a230ac8190920439076aaeb91e |
completed | April 9, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.