Triple
T33236359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaynagar–Janakpur–Bardibas railway line |
E850838
|
entity |
| Predicate | operatorInNepal |
P79316
|
FINISHED |
| Object | Nepal Railway Company |
—
|
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: Nepal Railway Company | Statement: [Jaynagar–Janakpur–Bardibas railway line, operatorInNepal, Nepal Railway Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorInNepal Context triple: [Jaynagar–Janakpur–Bardibas railway line, operatorInNepal, Nepal Railway Company]
-
A.
roleInNepal
Indicates that an entity holds or has held a specific role, position, or function within the context of Nepal.
-
B.
operatorInIndia
Indicates that an entity functions as an operator (such as a service provider or business operator) within the geographical region of India.
-
C.
entryPointFromNepal
Indicates that something serves as an entry point or access route originating from Nepal.
-
D.
otherOperator
Indicates a relationship where one operator is distinguished from, or serves as an alternative to, another operator within the same context or system.
-
E.
countryOperator
chosen
Indicates that an entity operates, manages, or runs services within a specified country.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
Created at: May 1, 2026, 1:31 a.m.