Triple
T30016745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Bhutan relations |
E762616
|
entity |
| Predicate | IndiaEmbassyLocationInBhutan |
P168358
|
FINISHED |
| Object | Thimphu |
—
|
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: Thimphu | Statement: [India–Bhutan relations, IndiaEmbassyLocationInBhutan, Thimphu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IndiaEmbassyLocationInBhutan Context triple: [India–Bhutan relations, IndiaEmbassyLocationInBhutan, Thimphu]
-
A.
overseesIndianConsulatesIn
Indicates that an entity has administrative authority or supervisory responsibility over Indian consulates located in a specified place or jurisdiction.
-
B.
haveEmbassyOfIndonesiaIn
Indicates that an entity hosts or contains an embassy representing Indonesia in a specified location.
-
C.
accessionToIndia
Indicates the act or process by which a territory, entity, or region formally joins or is incorporated into India.
-
D.
USEmbassyLocation
Indicates that a specified location is the site where the United States embassy for a particular country is situated.
-
E.
haveConsulatesOfIndonesiaIn
Indicates that consulates representing Indonesia are located within a specified place or jurisdiction.
- F. None of above. chosen
Provenance (4 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_69f6798536288190bd0541e060dd9f6a |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:46 p.m.