Triple
T30016747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Bhutan relations |
E762616
|
entity |
| Predicate | BhutanConsulateLocationInIndia |
P168359
|
FINISHED |
| Object | Kolkata |
—
|
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: Kolkata | Statement: [India–Bhutan relations, BhutanConsulateLocationInIndia, Kolkata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BhutanConsulateLocationInIndia Context triple: [India–Bhutan relations, BhutanConsulateLocationInIndia, Kolkata]
-
A.
BhutanEmbassyLocationInIndia
chosen
Indicates the location(s) within India where Bhutan’s embassy or official diplomatic mission is situated.
-
B.
IndiaEmbassyLocationInBhutan
Indicates the location within Bhutan where the Indian embassy is situated.
-
C.
overseesIndianConsulatesIn
Indicates that an entity has administrative authority or supervisory responsibility over Indian consulates located in a specified place or jurisdiction.
-
D.
borderingBhutaneseDistricts
Indicates that the specified Bhutanese districts share a common boundary with each other.
-
E.
capitalDzongOf
Indicates that one entity is the administrative capital (dzong) of a specified region or district.
- 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_69f6798536288190bd0541e060dd9f6a |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:46 p.m.