Triple

T28572467
Position Surface form Disambiguated ID Type / Status
Subject Burundian Armed Forces E723149 entity
Predicate hasBranch P35 FINISHED
Object Burundian Air Force
The Burundian Air Force is the aerial warfare branch of Burundi’s military, responsible for the country’s air defense, transport, and support operations.
E1828694 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: Burundian Air Force | Statement: [Burundian Armed Forces, hasBranch, Burundian Air Force]
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: Burundian Air Force
Triple: [Burundian Armed Forces, hasBranch, Burundian Air Force]
Generated description
The Burundian Air Force is the aerial warfare branch of Burundi’s military, responsible for the country’s air defense, transport, and support operations.

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_69f01d7e97708190ae9e77ee66a68abd completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f65093d9488190bc1e5c562b58f1e5 completed May 2, 2026, 7:29 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1cc36d8214819085c522ff31e5a22f completed May 31, 2026, 11:25 p.m.
NEDg Description generation batch_6a1cc44ac1448190b0dc305eb5e460be completed May 31, 2026, 11:29 p.m.
NED2 Entity disambiguation (via description) batch_6a1cc571b3b481908c523e5bad5e086a completed May 31, 2026, 11:34 p.m.
Created at: April 28, 2026, 4:10 a.m.