Triple
T37125004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darbhanga–Raxaul line |
E919365
|
entity |
| Predicate | borderTownServed |
P201461
|
FINISHED |
| Object | Raxaul |
—
|
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: Raxaul | Statement: [Darbhanga–Raxaul line, borderTownServed, Raxaul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTownServed Context triple: [Darbhanga–Raxaul line, borderTownServed, Raxaul]
-
A.
borderTownTerminus
Indicates a location that serves as the endpoint or terminal stop of a route situated in or at a border town.
-
B.
borderTownAccess
Indicates that an entity has permission or the ability to enter, use, or pass through a town located on or near a border.
-
C.
hasBorderTownRole
Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
-
D.
borderTerminus
Indicates the endpoint location where a border between two areas or entities begins or ends.
-
E.
isBorderTownBetween
Indicates that a town is located on or near the boundary separating two specified regions, serving as a border settlement between them.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
| PDg | Predicate description generation | batch_69fff86da6f48190aac10a80b648c05a |
completed | May 10, 2026, 3:15 a.m. |
Created at: May 3, 2026, 4:15 p.m.