Triple
T32256773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minotaur rocket family |
E824045
|
entity |
| Predicate | missionTypesInclude |
P22637
|
FINISHED |
| Object | technology demonstration |
—
|
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: technology demonstration | Statement: [Minotaur rocket family, missionTypesInclude, technology demonstration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionTypesInclude Context triple: [Minotaur rocket family, missionTypesInclude, technology demonstration]
-
A.
missionTypeSupport
Indicates that one entity provides support or assistance to another within the context of a specific mission or operation.
-
B.
typeOfMission
chosen
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
C.
missionTypeOnMaidenVoyage
Indicates the type or nature of the mission specifically during an entity’s maiden (first) voyage.
-
D.
planetaryMissionType
Indicates the specific category or nature of a mission conducted to explore or study a planet or planetary body.
-
E.
volareMissionAssociatedWith
Indicates that a Volare mission is linked or connected to another entity through an association or involvement relationship.
- 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_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:41 a.m.