Triple
T30009566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zokhawthar–Rikhawdar crossing |
E762419
|
entity |
| Predicate | borderSideSettlementInIndia |
P85285
|
FINISHED |
| Object | Zokhawthar |
—
|
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: Zokhawthar | Statement: [Zokhawthar–Rikhawdar crossing, borderSideSettlementInIndia, Zokhawthar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderSideSettlementInIndia Context triple: [Zokhawthar–Rikhawdar crossing, borderSideSettlementInIndia, Zokhawthar]
-
A.
hasBorderTownOnIndianSide
chosen
Indicates that a location has a corresponding town situated on the Indian side of an international border.
-
B.
borderingIndianStates
Indicates that one or more Indian states share a common land or maritime boundary with a given geographic or political entity.
-
C.
borderSettlement
Indicates that a settlement is located near or along a political or administrative border.
-
D.
borderTypeWithNepal
Indicates the specific nature or classification of the border relationship that an entity shares with Nepal.
-
E.
borderTradePointWith
Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 29, 2026, 6:43 p.m.