Triple
T33236358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaynagar–Janakpur–Bardibas railway line |
E850838
|
entity |
| Predicate | operatorInIndia |
P202277
|
FINISHED |
| Object | East Central Railway |
—
|
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: East Central Railway | Statement: [Jaynagar–Janakpur–Bardibas railway line, operatorInIndia, East Central Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorInIndia Context triple: [Jaynagar–Janakpur–Bardibas railway line, operatorInIndia, East Central Railway]
-
A.
scriptUsedInIndia
Indicates that a particular writing system or script is used within the geographical or cultural context of India.
-
B.
orderPrecedenceWithinIndia
Indicates the relative ranking or priority of entities in terms of legal or administrative precedence within the jurisdiction of India.
-
C.
IndiaProvides
Indicates that India supplies, offers, or makes available some resource, service, or benefit to another entity.
-
D.
manufacturerInIndia
Indicates that a manufacturer is located in or operates within India.
-
E.
legalCategoryInIndia
Indicates that an entity belongs to a specific legally defined category or classification under Indian law.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
| PDg | Predicate description generation | batch_6a006be382308190811a8ee29c262ba1 |
completed | May 10, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:31 a.m.