Triple
T16107058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samdrup Jongkhar District |
E390764
|
entity |
| Predicate | borderTypeWithIndia |
P58557
|
FINISHED |
| Object | land border |
—
|
LITERAL FINISHED |
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: land border | Statement: [Samdrup Jongkhar District, borderTypeWithIndia, land border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTypeWithIndia Context triple: [Samdrup Jongkhar District, borderTypeWithIndia, land border]
-
A.
hasBorderTownOnIndianSide
Indicates that a location has a corresponding town situated on the Indian side of an international border.
-
B.
borderTypeWithMongolia
Indicates the specific nature or classification of the border that an entity shares with Mongolia.
-
C.
borderingIndianStates
Indicates that one or more Indian states share a common land or maritime boundary with a given geographic or political entity.
-
D.
countryBorderType
chosen
Indicates the type or nature of the border relationship that exists between two countries.
-
E.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6e55c08190b77f344e4e8c42ad |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.