Triple
T29448177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A300-600ST |
E746905
|
entity |
| Predicate | specialDesignFeature |
P19394
|
FINISHED |
| Object | oversized cargo bay above main deck |
—
|
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: oversized cargo bay above main deck | Statement: [A300-600ST, specialDesignFeature, oversized cargo bay above main deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialDesignFeature Context triple: [A300-600ST, specialDesignFeature, oversized cargo bay above main deck]
-
A.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
B.
testedDesignFeature
Indicates that a specific design feature has been subjected to a test or evaluation process.
-
C.
usedDesignFeature
Indicates that one entity employed or incorporated a particular design feature in its creation, implementation, or functionality.
-
D.
specialFeature
chosen
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
-
E.
previousDesignFeature
Indicates that one design feature precedes another in a sequence or earlier version of a design.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 3:29 p.m.