Triple
T4140239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 541 |
E89252
|
entity |
| Predicate | upperStageConfiguration |
P12522
|
FINISHED |
| Object | single-engine Centaur |
—
|
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: single-engine Centaur | Statement: [Atlas V 541, upperStageConfiguration, single-engine Centaur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperStageConfiguration Context triple: [Atlas V 541, upperStageConfiguration, single-engine Centaur]
-
A.
upperStageStructure
Indicates that one entity functions as the upper structural stage or upper-level framework component of another entity.
-
B.
upperStageType
chosen
Indicates the type or classification of the upper stage in a multi-stage system or structure.
-
C.
upperStageVariant
Indicates that one upper stage is a specific version or configuration variant of another upper stage within a launch vehicle system.
-
D.
upperStageFamily
Indicates that one entity is classified as belonging to the same family or type of upper rocket stages as another entity.
-
E.
upperStageAcronym
Indicates that an entity has or is associated with an upper rocket stage identified by a specific acronym.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.