Triple
T32256746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minotaur I |
E824045
|
entity |
| Predicate | firstStageFrom |
P154333
|
FINISHED |
| Object | Minuteman II |
E1005840
|
NE 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: Minuteman II | Statement: [Minotaur I, firstStageFrom, Minuteman II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstStageFrom Context triple: [Minotaur I, firstStageFrom, Minuteman II]
-
A.
firstStageOrigin
chosen
Indicates that one entity is the original source or starting point of the first stage of another entity or process.
-
B.
firstStageType
Indicates that one entity is the type or category of the first stage or initial phase associated with another entity.
-
C.
firstStageName
Indicates that one entity is the initial or earliest stage name associated with another entity in a sequence or lifecycle.
-
D.
firstStageHost
Indicates that an entity serves as the initial host in a multi-stage process or lifecycle involving another entity.
-
E.
firstStageEngine
Indicates that an engine functions as the primary propulsion unit used in the first stage of a multi-stage launch vehicle or rocket.
- F. None of above.
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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f46d5d8b881908c63c993b12eddb6 |
completed | June 15, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:41 a.m.