Triple
T34505094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raxaul subdivision |
E885861
|
entity |
| Predicate | borderStateOnNepalSide |
P199939
|
FINISHED |
| Object | Madhesh Province |
—
|
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: Madhesh Province | Statement: [Raxaul subdivision, borderStateOnNepalSide, Madhesh Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderStateOnNepalSide Context triple: [Raxaul subdivision, borderStateOnNepalSide, Madhesh Province]
-
A.
hasBorderTownOnNepaliSide
Indicates that a location has a corresponding town situated on the Nepali side of an international border.
-
B.
borderTypeWithNepal
Indicates the specific nature or classification of the border relationship that an entity shares with Nepal.
-
C.
bordersAdministrativeRegionOfNepal
Indicates that one administrative region of Nepal shares a common boundary with another administrative region of Nepal.
-
D.
borderingBhutaneseDistricts
Indicates that the specified Bhutanese districts share a common boundary with each other.
-
E.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
| PDg | Predicate description generation | batch_69ff64b864f481909fcefc2b08595c89 |
completed | May 9, 2026, 4:45 p.m. |
Created at: May 1, 2026, 2:01 a.m.