Triple
T30016793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Bhutan relations |
E762616
|
entity |
| Predicate | IndiaAndBhutanHold |
P172835
|
FINISHED |
| Object | regular high-level visits |
—
|
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: regular high-level visits | Statement: [India–Bhutan relations, IndiaAndBhutanHold, regular high-level visits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IndiaAndBhutanHold Context triple: [India–Bhutan relations, IndiaAndBhutanHold, regular high-level visits]
-
A.
IndiaAndBhutanCoordinateOn
chosen
Indicates that India and Bhutan work together in a planned and cooperative manner on a specific issue, activity, or policy area.
-
B.
IndiaBackedBhutanOn
Indicates that India provided support to Bhutan regarding a specific issue, position, or action.
-
C.
borderingIndianStates
Indicates that one or more Indian states share a common land or maritime boundary with a given geographic or political entity.
-
D.
IndiaProvides
Indicates that India supplies, offers, or makes available some resource, service, or benefit to another entity.
-
E.
borderingBhutaneseDistricts
Indicates that the specified Bhutanese districts share a common boundary with each other.
- 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_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 6:46 p.m.