Triple
T30877210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proton |
E786509
|
entity |
| Predicate | typicalUpperStage |
P56081
|
FINISHED |
| Object | Briz-M |
E408520
|
NE 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: Briz-M | Statement: [Proton, typicalUpperStage, Briz-M]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUpperStage Context triple: [Proton, typicalUpperStage, Briz-M]
-
A.
upperStageFamily
Indicates that one entity is classified as belonging to the same family or type of upper rocket stages as another entity.
-
B.
upperStageType
Indicates the type or classification of the upper stage in a multi-stage system or structure.
-
C.
compatibleUpperStage
chosen
Indicates that one stage of a launch vehicle can function correctly and safely as the upper stage when paired with a given lower stage or booster.
-
D.
upperStageVariant
Indicates that one upper stage is a specific version or configuration variant of another upper stage within a launch vehicle system.
-
E.
upperStageRole
Indicates the functional role or purpose that a stage plays within the upper portion of a multi-stage system or structure.
- F. None of above.
Provenance (4 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28c7dfb7548190a607efecaf9c9bf5 |
completed | June 10, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:48 p.m.