Triple
T35038491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 400 series |
E1010995
|
entity |
| Predicate | usesPayloadFairingType |
P143663
|
FINISHED |
| Object | 4-meter 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: 4-meter payload fairing | Statement: [Atlas V 400 series, usesPayloadFairingType, 4-meter payload fairing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPayloadFairingType Context triple: [Atlas V 400 series, usesPayloadFairingType, 4-meter payload fairing]
-
A.
usesPayload
Indicates that one entity employs or utilizes another entity as its payload in performing an action or function.
-
B.
hasPayloadFairing
Indicates that one entity is equipped with, or includes, a payload fairing associated with another entity.
-
C.
payloadFairingType
chosen
Indicates the specific type or configuration of the payload fairing used to enclose and protect a payload during launch.
-
D.
usedPayloadBay
Indicates that an entity made use of another entity’s payload bay to carry, store, or deploy cargo or equipment.
-
E.
compatiblePayload
Indicates that one entity can be safely or effectively used as the payload of another entity without conflict or required modification.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:01 p.m.