Triple
T6486751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadair Challenger |
E146530
|
entity |
| Predicate | fuselageDesign |
P11768
|
FINISHED |
| Object | wide cross‑section for class |
—
|
LITERAL 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: wide cross‑section for class | Statement: [Canadair Challenger, fuselageDesign, wide cross‑section for class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuselageDesign Context triple: [Canadair Challenger, fuselageDesign, wide cross‑section for class]
-
A.
fuselageShape
Indicates the geometric form or contour of an object's fuselage, describing how its main body is shaped.
-
B.
fuselageType
chosen
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
C.
fuselageCount
Indicates the number of fuselages associated with or contained in an aircraft or aerospace structure.
-
D.
fuselageDiameter
Indicates the diameter measurement of an aircraft’s fuselage in the described context.
-
E.
airframeDesigner
Indicates that one entity is the designer or design authority responsible for the airframe of an aircraft or aerospace vehicle associated with the other entity.
- F. None of above.
Provenance (3 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a706d4c8190b7a3cc8855abcecb |
completed | March 22, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:52 p.m.