Triple
T33081131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Cryogenic Second Stage |
E846509
|
entity |
| Predicate | fairingInterface |
P175784
|
FINISHED |
| Object | Delta IV payload fairing |
—
|
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: Delta IV payload fairing | Statement: [Delta Cryogenic Second Stage, fairingInterface, Delta IV payload fairing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fairingInterface Context triple: [Delta Cryogenic Second Stage, fairingInterface, Delta IV payload fairing]
-
A.
fairingType
Indicates the specific kind or design category of a fairing used in a structure, vehicle, or assembly.
-
B.
fairingManufacturer
Indicates that one entity is the manufacturer or producer of the fairing used by another entity (such as a vehicle, rocket, or component).
-
C.
fairingHeight
Indicates the vertical dimension or distance from base to top of a fairing structure.
-
D.
fairingSeparation
Indicates the event or relationship in which a protective fairing is detached or separated from the object it was enclosing.
-
E.
fairingDiameterClass
Indicates the classification of an object based on the size range of its fairing diameter.
- F. None of above. chosen
Provenance (4 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:26 a.m.