Triple
T30016786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Bhutan relations |
E762616
|
entity |
| Predicate | IndiaIsKeySourceOf |
P169345
|
FINISHED |
| Object | Bhutanese imports |
—
|
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: Bhutanese imports | Statement: [India–Bhutan relations, IndiaIsKeySourceOf, Bhutanese imports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IndiaIsKeySourceOf Context triple: [India–Bhutan relations, IndiaIsKeySourceOf, Bhutanese imports]
-
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.
accessionToIndia
Indicates the act or process by which a territory, entity, or region formally joins or is incorporated into India.
-
D.
scriptUsedInIndia
Indicates that a particular writing system or script is used within the geographical or cultural context of India.
-
E.
introducedToIndiaBy
Indicates that something was brought or made known to India by a particular agent, source, or intermediary.
- 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_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 6:46 p.m.