Triple
T16496711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kosmos-3M |
E400700
|
entity |
| Predicate | firstStageRole |
P50951
|
FINISHED |
| Object | initial ascent and boost phase |
—
|
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: initial ascent and boost phase | Statement: [Kosmos-3M, firstStageRole, initial ascent and boost phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstStageRole Context triple: [Kosmos-3M, firstStageRole, initial ascent and boost phase]
-
A.
firstStageName
Indicates that one entity is the initial or earliest stage name associated with another entity in a sequence or lifecycle.
-
B.
firstStageType
Indicates that one entity is the type or category of the first stage or initial phase associated with another entity.
-
C.
firstStageDescription
chosen
Indicates that the value provides a textual explanation or summary of the initial or earliest stage in a multi-stage process or sequence.
-
D.
upperStageRole
Indicates the functional role or purpose that a stage plays within the upper portion of a multi-stage system or structure.
-
E.
earlyRole
Indicates that an entity held a particular role or position during an early or initial stage of its involvement or development.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e343a7c81909e04cbaaa40e2531 |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.