Triple
T22532639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B39M |
E557077
|
entity |
| Predicate | associatedWithFuselageType |
P11768
|
FINISHED |
| Object | single‑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: single‑aisle | Statement: [B39M, associatedWithFuselageType, single‑aisle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFuselageType Context triple: [B39M, associatedWithFuselageType, single‑aisle]
-
A.
fuselageType
chosen
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
B.
fuselageVariant
Indicates that one fuselage is a specific version or variant derived from another fuselage design.
-
C.
associatedWithCarrierAircraft
Indicates a relationship where something is linked or connected to a carrier-based aircraft, such as being used by, transported on, or otherwise functionally related to it.
-
D.
associatedWithAircraftModel
Indicates that something has a specified relationship or connection to a particular aircraft model.
-
E.
fuselageShape
Indicates the geometric form or contour of an object's fuselage, describing how its main body is shaped.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed88cf08190ae7e5b6bf9a80372 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.