Triple
T35087555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blok D upper stage |
E1012617
|
entity |
| Predicate | reignitionMethod |
P43929
|
FINISHED |
| Object | ullage and restartable main engine |
—
|
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: ullage and restartable main engine | Statement: [Blok D upper stage, reignitionMethod, ullage and restartable main engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignitionMethod Context triple: [Blok D upper stage, reignitionMethod, ullage and restartable main engine]
-
A.
ignitionMethod
chosen
Indicates the specific way or mechanism by which something is ignited or set on fire.
-
B.
ignitionPhase
Indicates the phase or stage of the ignition process that an entity is currently in or associated with.
-
C.
methodOfRejuvenation
Indicates a process or technique used to restore youthfulness, vitality, or an earlier optimal state to something or someone.
-
D.
reignRestart
Indicates that a ruler’s period of governance has begun again after an interruption or previous end.
-
E.
detonationMethod
Indicates the method or mechanism by which an explosive device is triggered or detonated.
- 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_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:01 p.m.