Triple

T36348301
Position Surface form Disambiguated ID Type / Status
Subject Dagger C E895124 entity
Predicate usedBy P260 FINISHED
Object Grupo 8 de Caza (Argentine Air Force unit)
Grupo 8 de Caza is an Argentine Air Force fighter unit known for operating advanced combat aircraft such as the Dagger C.
E2182884 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: Grupo 8 de Caza (Argentine Air Force unit) | Statement: [Dagger C, usedBy, Grupo 8 de Caza (Argentine Air Force unit)]
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: Grupo 8 de Caza (Argentine Air Force unit)
Triple: [Dagger C, usedBy, Grupo 8 de Caza (Argentine Air Force unit)]
Generated description
Grupo 8 de Caza is an Argentine Air Force fighter unit known for operating advanced combat aircraft such as the Dagger C.

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_69f76e4f437c8190a1af3ea2564f41f5 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7baa3104081909890bac7250a79f5 completed May 3, 2026, 9:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39b4290b148190b1890397fd8ea8da completed June 22, 2026, 10:16 p.m.
NEDg Description generation batch_6a39b9f7375c8190b3a5d359707ba074 completed June 22, 2026, 10:40 p.m.
NED2 Entity disambiguation (via description) batch_6a39bc9a018881908011f4b76f0eb7db completed June 22, 2026, 10:52 p.m.
Created at: May 3, 2026, 4:09 p.m.