Triple

T32374522
Position Surface form Disambiguated ID Type / Status
Subject Falcon 2000EX EASy E827239 entity
Predicate successor P78 FINISHED
Object Falcon 2000LXS
The Falcon 2000LXS is a long-range, twin-engine business jet by Dassault Aviation known for its efficient performance, advanced avionics, and ability to operate from short runways.
E2008379 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: Falcon 2000LXS | Statement: [Falcon 2000EX EASy, successor, Falcon 2000LXS]
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: Falcon 2000LXS
Triple: [Falcon 2000EX EASy, successor, Falcon 2000LXS]
Generated description
The Falcon 2000LXS is a long-range, twin-engine business jet by Dassault Aviation known for its efficient performance, advanced avionics, and ability to operate from short runways.

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_69f349177ddc8190ab0583f05597056b completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c12eb9b88190b6d1a371081717b0 completed May 3, 2026, 3:29 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3466690f708190879f2b9ce9e3d7d3 completed June 18, 2026, 9:43 p.m.
NEDg Description generation batch_6a346712d6408190897672c47396895f completed June 18, 2026, 9:45 p.m.
NED2 Entity disambiguation (via description) batch_6a3467df74088190b9d033e1534876c6 completed June 18, 2026, 9:49 p.m.
Created at: May 1, 2026, 12:50 a.m.