Triple
T633228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 747SP |
E15965
|
entity |
| Predicate | fuselageConfiguration |
P11768
|
FINISHED |
| Object | twin-aisle |
—
|
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: twin-aisle | Statement: [Boeing 747SP, fuselageConfiguration, twin-aisle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuselageConfiguration Context triple: [Boeing 747SP, fuselageConfiguration, twin-aisle]
-
A.
fuselageType
chosen
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
B.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
-
C.
wingConfiguration
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
-
D.
hasWingConfiguration
Indicates how an entity’s wings are arranged, structured, or configured relative to its body or to each other.
-
E.
airframe
Indicates that an entity is the structural framework or body of an aircraft associated with another entity (such as a specific model, component, or system).
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec3b6488190aa0dce216c089a2e |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.