Triple
T22532638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B39M |
E557077
|
entity |
| Predicate | associatedWithWingConfiguration |
P7143
|
FINISHED |
| Object | low‑wing |
—
|
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: low‑wing | Statement: [B39M, associatedWithWingConfiguration, low‑wing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWingConfiguration Context triple: [B39M, associatedWithWingConfiguration, low‑wing]
-
A.
hasWingConfiguration
chosen
Indicates how an entity’s wings are arranged, structured, or configured relative to its body or to each other.
-
B.
wingConfiguration
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
-
C.
hasWingIn
Indicates that an entity possesses a wing that is located in or contained within another specified entity or structure.
-
D.
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.
-
E.
airWingType
Indicates the classification or category of an air wing associated with an 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_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.