Triple
T30016778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Bhutan relations |
E762616
|
entity |
| Predicate | IndiaSupportsBhutanIn |
P169345
|
FINISHED |
| Object | telecommunications and ICT development |
—
|
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: telecommunications and ICT development | Statement: [India–Bhutan relations, IndiaSupportsBhutanIn, telecommunications and ICT development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IndiaSupportsBhutanIn Context triple: [India–Bhutan relations, IndiaSupportsBhutanIn, telecommunications and ICT development]
-
A.
BhutanEmbassyLocationInIndia
Indicates the location(s) within India where Bhutan’s embassy or official diplomatic mission is situated.
-
B.
IndiaProvides
chosen
Indicates that India supplies, offers, or makes available some resource, service, or benefit to another entity.
-
C.
IndiaEmbassyLocationInBhutan
Indicates the location within Bhutan where the Indian embassy is situated.
-
D.
declaresIndiaAs
Indicates that a subject formally designates or proclaims something or someone as India.
-
E.
diplomaticSupportFrom
Indicates that one entity provides diplomatic backing, advocacy, or assistance to another in international or political affairs.
- 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_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 6:46 p.m.