Triple
T8630947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A3ST |
E204399
|
entity |
| Predicate | aircraftWingConfiguration |
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: [A3ST, aircraftWingConfiguration, low-wing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftWingConfiguration Context triple: [A3ST, aircraftWingConfiguration, low-wing]
-
A.
wingConfiguration
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
-
B.
hasWingConfiguration
chosen
Indicates how an entity’s wings are arranged, structured, or configured relative to its body or to each other.
-
C.
typeOfWing
Indicates the specific kind or category of wing that an entity possesses or is associated with.
-
D.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
-
E.
wingSweepAngles
Indicates the angular positions of an entity’s wings relative to a reference axis, typically describing how far the wings are swept forward or backward.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.