Triple
T30016769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Bhutan relations |
E762616
|
entity |
| Predicate | IndiaMaintains |
P169345
|
FINISHED |
| Object | Indian Military Training Team in Bhutan |
—
|
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: Indian Military Training Team in Bhutan | Statement: [India–Bhutan relations, IndiaMaintains, Indian Military Training Team in Bhutan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IndiaMaintains Context triple: [India–Bhutan relations, IndiaMaintains, Indian Military Training Team in Bhutan]
-
A.
IndiaProvides
chosen
Indicates that India supplies, offers, or makes available some resource, service, or benefit to another entity.
-
B.
IndianCenter
Indicates that something serves as a central or primary hub related to India or Indian affairs.
-
C.
declaresIndiaAs
Indicates that a subject formally designates or proclaims something or someone as India.
-
D.
stateInIndia
Indicates that a given state is located within the country of India.
-
E.
borderingIndianStates
Indicates that one or more Indian states share a common land or maritime boundary with a given geographic or political 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 6:46 p.m.