Triple

T37962848
Position Surface form Disambiguated ID Type / Status
Subject Ikarus (aircraft manufacturer) E947051 entity
Predicate notableProduct P1448 FINISHED
Object Ikarus 451
The Ikarus 451 is a Yugoslav experimental jet-powered research aircraft developed in the early Cold War era to test advanced aerodynamic and propulsion concepts.
E947051 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: Ikarus 451 | Statement: [Ikarus (aircraft manufacturer), notableProduct, Ikarus 451]
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: Ikarus 451
Triple: [Ikarus (aircraft manufacturer), notableProduct, Ikarus 451]
Generated description
The Ikarus 451 is a Yugoslav experimental jet-powered research aircraft developed in the early Cold War era to test advanced aerodynamic and propulsion concepts.

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_69f76ef7062c819091bfacb7e83aa1e0 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbbdd918b08190ba26d51eeb5e183f completed May 6, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41542c1ea0819085f5c8745031087e completed June 28, 2026, 5:04 p.m.
NEDg Description generation batch_6a4154f9bd488190bd99bf83b6073655 completed June 28, 2026, 5:08 p.m.
NED2 Entity disambiguation (via description) batch_6a41557755e48190b67b61fb381580a7 completed June 28, 2026, 5:10 p.m.
Created at: May 3, 2026, 4:20 p.m.