Triple
T33236349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaynagar–Janakpur–Bardibas railway line |
E850838
|
entity |
| Predicate | terminusInIndia |
P388
|
FINISHED |
| Object | Jaynagar |
—
|
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: Jaynagar | Statement: [Jaynagar–Janakpur–Bardibas railway line, terminusInIndia, Jaynagar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusInIndia Context triple: [Jaynagar–Janakpur–Bardibas railway line, terminusInIndia, Jaynagar]
-
A.
terminusInland
Indicates that something ends, concludes, or has its final point within an inland area rather than at a coast or shoreline.
-
B.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
C.
terminusLocatedOn
Indicates that the endpoint or final stop of one entity (such as a route or line) is situated on or at another entity (such as a street, line, or location).
-
D.
terminus
chosen
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
E.
terminusConnectsTo
Indicates that a transportation route’s endpoint is directly linked or transitions to another route, line, or terminal.
- 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_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:31 a.m.