Triple
T26281619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulfstream G800 |
E660712
|
entity |
| Predicate | hasWingDesign |
P7143
|
FINISHED |
| Object | high-aspect-ratio 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: high-aspect-ratio wing | Statement: [Gulfstream G800, hasWingDesign, high-aspect-ratio wing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWingDesign Context triple: [Gulfstream G800, hasWingDesign, high-aspect-ratio wing]
-
A.
hasWingOf
Indicates that one entity possesses or is associated with the wing that belongs to another entity.
-
B.
hasWingConfiguration
chosen
Indicates how an entity’s wings are arranged, structured, or configured relative to its body or 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.
hasWingFunction
Indicates that an entity possesses a wing and specifies the functional role or purpose that the wing serves.
-
E.
hasWingsMadeOf
Indicates that one entity has wings whose material or composition is made from the other 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 10:01 p.m.