Triple
T30017051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Bhutan Army |
E762622
|
entity |
| Predicate | equipmentSupportFrom |
P96016
|
FINISHED |
| Object | India |
—
|
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: India | Statement: [Royal Bhutan Army, equipmentSupportFrom, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentSupportFrom Context triple: [Royal Bhutan Army, equipmentSupportFrom, India]
-
A.
supportedEquipment
Indicates that one entity provides compatibility with, or operational support for, a specified piece of equipment.
-
B.
vendorSupportStatus
Indicates the current level or state of support provided by a vendor for a product, service, or customer.
-
C.
equipmentProvider
chosen
Indicates that one entity supplies or makes available equipment for use by another entity.
-
D.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
E.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
- 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_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:46 p.m.