Triple
T25182534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegasus Airlines Flight 2193 |
E630621
|
entity |
| Predicate | fuselageSections |
P54374
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Pegasus Airlines Flight 2193, fuselageSections, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuselageSections Context triple: [Pegasus Airlines Flight 2193, fuselageSections, 3]
-
A.
fuselageShape
Indicates the geometric form or contour of an object's fuselage, describing how its main body is shaped.
-
B.
fuselageVariant
Indicates that one fuselage is a specific version or variant derived from another fuselage design.
-
C.
fuselageType
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
D.
fuselageCount
chosen
Indicates the number of fuselages associated with or contained in an aircraft or aerospace structure.
-
E.
fuselageDesignBasisFor
Indicates that a particular fuselage design serves as the foundational basis or reference model for another design, configuration, or derived element.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc784448190ba2ef45b1d688ec9 |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:36 p.m.