Triple

T38294714
Position Surface form Disambiguated ID Type / Status
Subject Anti-Corruption Commission of Bhutan E1022457 entity
Predicate shortName P43 FINISHED
Object ACC Bhutan
ACC Bhutan is Bhutan’s independent Anti-Corruption Commission responsible for preventing, investigating, and combating corruption in the country.
E2264893 NE 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: ACC Bhutan | Statement: [Anti-Corruption Commission of Bhutan, shortName, ACC Bhutan]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: ACC Bhutan
Triple: [Anti-Corruption Commission of Bhutan, shortName, ACC Bhutan]
Generated description
ACC Bhutan is Bhutan’s independent Anti-Corruption Commission responsible for preventing, investigating, and combating corruption in the country.

Provenance (5 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_69f76df190f081908d5aa02c8a9286d0 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcc6151d4481909a7d012ab440c4f3 completed May 7, 2026, 5:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a419e01adc081908f43d31feae9c1f5 completed June 28, 2026, 10:19 p.m.
NEDg Description generation batch_6a41a00f9eac8190823c96ff6f7c8941 completed June 28, 2026, 10:28 p.m.
NED2 Entity disambiguation (via description) batch_6a41a05dbf248190adffdb8ecf42d5c6 completed June 28, 2026, 10:29 p.m.
Created at: May 3, 2026, 4:30 p.m.