Triple
T30016760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Bhutan relations |
E762616
|
entity |
| Predicate | IndiaProvides |
P169345
|
FINISHED |
| Object | budgetary support to Bhutan |
—
|
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: budgetary support to Bhutan | Statement: [India–Bhutan relations, IndiaProvides, budgetary support to Bhutan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IndiaProvides Context triple: [India–Bhutan relations, IndiaProvides, budgetary support to Bhutan]
-
A.
IndianCenter
Indicates that something serves as a central or primary hub related to India or Indian affairs.
-
B.
declaresIndiaAs
Indicates that a subject formally designates or proclaims something or someone as India.
-
C.
viewsIndiaAs
Indicates perceiving or regarding India in a particular way, such as holding a specific opinion, attitude, or characterization about India.
-
D.
foundedInSubcontinent
Indicates that an entity was founded or established within a specific geographic subcontinent.
-
E.
partlyLocatedInIndianState
Indicates that an entity is geographically or administratively situated such that only part of it lies within the boundaries of a specified Indian state.
- 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_69f67de7792c81909b5e4e812d143624 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 6:46 p.m.