Triple
T6788970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-125 Neva/Pechora |
E155883
|
entity |
| Predicate | missileStages |
P73001
|
FINISHED |
| Object | two-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: two-stage | Statement: [S-125 Neva/Pechora, missileStages, two-stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missileStages Context triple: [S-125 Neva/Pechora, missileStages, two-stage]
-
A.
thirdStagePropellant
Indicates that an entity serves as the propellant used in the third stage of a multi-stage rocket or launch vehicle.
-
B.
enginesUpperStage
Indicates that the specified engines are part of, or belong to, the upper stage of a multi-stage launch vehicle or rocket.
-
C.
numberOfFirstStageEngines
Indicates the quantity of engines used in the first stage of a multi-stage system or vehicle.
-
D.
propellantStage3
Indicates that an entity serves as or is associated with the third stage of a multi-stage propellant or propulsion system.
-
E.
missileLength
Indicates the physical longitudinal measurement of a missile from one end to the other.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2aa2e0c8190b994261826ae001d |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1b0d2a48190b249dcc671b9b5e4 |
completed | March 27, 2026, 6:51 p.m. |
Created at: March 27, 2026, 2:14 p.m.