Triple
T29817891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jogbani–Biratnagar crossing |
E757160
|
entity |
| Predicate | hasBorderTownOnNepaliSide |
P188885
|
FINISHED |
| Object | Biratnagar |
—
|
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: Biratnagar | Statement: [Jogbani–Biratnagar crossing, hasBorderTownOnNepaliSide, Biratnagar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderTownOnNepaliSide Context triple: [Jogbani–Biratnagar crossing, hasBorderTownOnNepaliSide, Biratnagar]
-
A.
hasBorderTownOnIndianSide
Indicates that a location has a corresponding town situated on the Indian side of an international border.
-
B.
hasBorderTownOnMyanmarSide
Indicates that a town is located on the Myanmar side of a border shared with another country.
-
C.
borderTypeWithNepal
Indicates the specific nature or classification of the border relationship that an entity shares with Nepal.
-
D.
bordersAdministrativeRegionOfNepal
Indicates that one administrative region of Nepal shares a common boundary with another administrative region of Nepal.
-
E.
hasBorderTownOnCanadianSide
Indicates that one location has a corresponding border town situated on the Canadian side of an international boundary.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: April 29, 2026, 5:27 p.m.