Triple
T35087551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blok D upper stage |
E1012617
|
entity |
| Predicate | typicalMissionPhase |
P184641
|
FINISHED |
| Object | post-orbital injection |
—
|
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: post-orbital injection | Statement: [Blok D upper stage, typicalMissionPhase, post-orbital injection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMissionPhase Context triple: [Blok D upper stage, typicalMissionPhase, post-orbital injection]
-
A.
missionProfilePhase
chosen
Indicates the specific phase or stage within a mission profile during which an action, condition, or relationship is applicable.
-
B.
coversMissionPhase
Indicates that one entity’s scope, responsibility, or applicability extends over a specified mission phase.
-
C.
currentMissionPhase
Indicates the specific phase or stage that a mission is presently in within its overall lifecycle.
-
D.
missionPhaseAfter
Indicates that one mission phase occurs later in sequence or time than another mission phase.
-
E.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.