Triple

T35556767
Position Surface form Disambiguated ID Type / Status
Subject Ilyushin E1027518 entity
Predicate product P490 FINISHED
Object Ilyushin Il-80
The Ilyushin Il-80 is a Russian airborne command post aircraft, often called a "doomsday plane," designed to ensure national command and control in the event of nuclear war or other large-scale conflicts.
E2223707 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: Ilyushin Il-80 | Statement: [Ilyushin, product, Ilyushin Il-80]
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: Ilyushin Il-80
Triple: [Ilyushin, product, Ilyushin Il-80]
Generated description
The Ilyushin Il-80 is a Russian airborne command post aircraft, often called a "doomsday plane," designed to ensure national command and control in the event of nuclear war or other large-scale conflicts.

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_69f76e014fd481909e9f04ac603a2aa9 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7983fd11c8190a3006e42abe3dfec completed May 3, 2026, 6:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a406cb80ab48190b9421e53f275454a completed June 28, 2026, 12:37 a.m.
NEDg Description generation batch_6a406defac38819086c2585b63b93dde completed June 28, 2026, 12:42 a.m.
NED2 Entity disambiguation (via description) batch_6a406e7763b081908b37db6d670f2084 completed June 28, 2026, 12:44 a.m.
Created at: May 3, 2026, 4:04 p.m.