Triple
T35038498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 400 series |
E1010995
|
entity |
| Predicate | hasOptionalComponent |
P23744
|
FINISHED |
| Object | solid rocket booster |
—
|
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: solid rocket booster | Statement: [Atlas V 400 series, hasOptionalComponent, solid rocket booster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOptionalComponent Context triple: [Atlas V 400 series, hasOptionalComponent, solid rocket booster]
-
A.
hasOptionalSection
chosen
Indicates that an entity includes a section or component that is not mandatory and may or may not be present.
-
B.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
-
C.
hasComponentForm
Indicates that one entity exists as a structural or compositional form or variant of another entity.
-
D.
hasSecondaryComponent
Indicates that an entity includes or is associated with an additional, subordinate component beyond its primary one.
-
E.
hasOptionalProtocol
Indicates that an entity may, but is not required to, follow or support a specified protocol.
- 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_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:01 p.m.