Triple
T32256748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minotaur I |
E824045
|
entity |
| Predicate | upperStagesFrom |
P24963
|
FINISHED |
| Object | Pegasus rocket |
—
|
NE NERFINISHED |
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: Pegasus rocket | Statement: [Minotaur I, upperStagesFrom, Pegasus rocket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperStagesFrom Context triple: [Minotaur I, upperStagesFrom, Pegasus rocket]
-
A.
upperLevels
Indicates that one entity occupies or corresponds to higher levels, tiers, or hierarchical positions relative to another entity.
-
B.
upperCourseOf
Indicates that one watercourse represents the upstream or higher-elevation segment of another watercourse within the same river system.
-
C.
upperStageVariant
chosen
Indicates that one upper stage is a specific version or configuration variant of another upper stage within a launch vehicle system.
-
D.
upperStageType
Indicates the type or classification of the upper stage in a multi-stage system or structure.
-
E.
upperLevelStatus
Indicates that one entity holds a higher-level, superior, or overarching status relative to another within a hierarchy or layered structure.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc549ce88190963037034412e0b1 |
completed | May 3, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:41 a.m.