Triple
T14133311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulfstream G600 |
E350222
|
entity |
| Predicate | compositeUse |
P9772
|
FINISHED |
| Object | composite empennage and control surfaces |
—
|
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: composite empennage and control surfaces | Statement: [Gulfstream G600, compositeUse, composite empennage and control surfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositeUse Context triple: [Gulfstream G600, compositeUse, composite empennage and control surfaces]
-
A.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
B.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
C.
combinationType
Indicates how multiple elements are combined or related to each other within a composite structure or operation.
-
D.
usedComponent
chosen
Indicates that one entity has employed or incorporated another entity as a component in its structure, function, or operation.
-
E.
combinesFeaturesOf
Indicates that one entity integrates or merges characteristics, attributes, or functionalities originating from multiple other entities.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610cece88190b4a86500677e5938 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 11:34 p.m.