Triple
T29648651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rikhawdar |
E756073
|
entity |
| Predicate | hasBorderInteractionWith |
P23990
|
FINISHED |
| Object | nearby Indian border settlements |
—
|
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: nearby Indian border settlements | Statement: [Rikhawdar, hasBorderInteractionWith, nearby Indian border settlements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderInteractionWith Context triple: [Rikhawdar, hasBorderInteractionWith, nearby Indian border settlements]
-
A.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
B.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
C.
hasBorderConnection
chosen
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
D.
hasBorderConflictWith
Indicates a relationship where two entities share a disputed boundary or are involved in an ongoing or historical conflict over their common border.
-
E.
operatesOnBorderWith
Indicates that one entity conducts activities or exerts influence along or across the shared border it has with another entity.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 28, 2026, 6:51 p.m.