Triple
T4118262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stratolaunch carrier aircraft |
E90345
|
entity |
| Predicate | centralWingSectionUse |
P35274
|
FINISHED |
| Object | payload mounting |
—
|
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: payload mounting | Statement: [Stratolaunch carrier aircraft, centralWingSectionUse, payload mounting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralWingSectionUse Context triple: [Stratolaunch carrier aircraft, centralWingSectionUse, payload mounting]
-
A.
fuselageType
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
B.
hasCentralSection
chosen
Indicates that an entity possesses a distinct middle or central part within its overall structure or composition.
-
C.
wingConfiguration
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
-
D.
architectOfWing
Indicates that one entity served as the architect responsible for designing a particular wing of a building or structure.
-
E.
hasArmedWing
Indicates that an entity maintains, controls, or is associated with an organized armed or military wing.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.