Triple
T17245860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H3-30 |
E418622
|
entity |
| Predicate | upperStageCount |
P84404
|
FINISHED |
| Object | one upper stage |
—
|
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: one upper stage | Statement: [H3-30, upperStageCount, one upper stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperStageCount Context triple: [H3-30, upperStageCount, one upper stage]
-
A.
upperStageType
Indicates the type or classification of the upper stage in a multi-stage system or structure.
-
B.
upperStageStructure
Indicates that one entity functions as the upper structural stage or upper-level framework component of another entity.
-
C.
upperStageCapability
Indicates the capability or performance characteristics of an upper stage in a multi-stage system (such as a launch vehicle) relative to its intended functions or missions.
-
D.
launchVehicleStageCount
chosen
Indicates the number of distinct stages that a launch vehicle has in its configuration or design.
-
E.
upperStageFamily
Indicates that one entity is classified as belonging to the same family or type of upper rocket stages as another entity.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e23b8948190870d0e6b4e55b4e3 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.