Triple

T29118240
Position Surface form Disambiguated ID Type / Status
Subject Armed Forces of Mongolia E737104 entity
Predicate hasTrainingExercise P105437 FINISHED
Object Steppe Eagle
Steppe Eagle is a multinational military training exercise focused on enhancing interoperability and readiness among participating armed forces.
E1851785 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: Steppe Eagle | Statement: [Armed Forces of Mongolia, hasTrainingExercise, Steppe Eagle]
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: Steppe Eagle
Triple: [Armed Forces of Mongolia, hasTrainingExercise, Steppe Eagle]
Generated description
Steppe Eagle is a multinational military training exercise focused on enhancing interoperability and readiness among participating armed forces.

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_69f077ed54e08190bb02a744e8121a66 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69fdb39baf0c8190871cdd4b080de6f7 completed May 8, 2026, 9:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2537ca9fd4819082b8559c2b00d38d completed June 7, 2026, 9:20 a.m.
NEDg Description generation batch_6a253bf87598819087116abf2274d649 completed June 7, 2026, 9:38 a.m.
NED2 Entity disambiguation (via description) batch_6a25470a98f48190b7afa02e39675cc3 completed June 7, 2026, 10:25 a.m.
Created at: April 28, 2026, 11:23 a.m.