Triple
T33236350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaynagar–Janakpur–Bardibas railway line |
E850838
|
entity |
| Predicate | terminusInNepal |
P388
|
FINISHED |
| Object | Bardibas |
—
|
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: Bardibas | Statement: [Jaynagar–Janakpur–Bardibas railway line, terminusInNepal, Bardibas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusInNepal Context triple: [Jaynagar–Janakpur–Bardibas railway line, terminusInNepal, Bardibas]
-
A.
entryPointFromNepal
Indicates that something serves as an entry point or access route originating from Nepal.
-
B.
terminus
chosen
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
C.
terminusResort
Indicates that one entity serves as the final destination or endpoint location (terminus) associated with a particular resort.
-
D.
terminusWestCountry
Indicates that something serves as the western endpoint or final stop of a route, line, or connection within the West Country region.
-
E.
distanceFromKathmandu
Indicates the measured spatial distance between a given location or entity and the city of Kathmandu.
- 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_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 1, 2026, 1:31 a.m.