Triple
T18039255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angara |
E431596
|
entity |
| Predicate | launchVehicleFamilyFor |
P4020
|
FINISHED |
| Object | Russian military payloads |
—
|
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: Russian military payloads | Statement: [Angara, launchVehicleFamilyFor, Russian military payloads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchVehicleFamilyFor Context triple: [Angara, launchVehicleFamilyFor, Russian military payloads]
-
A.
launchVehicleProvider
Indicates the entity that supplies or operates the launch vehicle used to carry a payload into space.
-
B.
launchVehicleFamilyAbbreviation
Indicates the abbreviated designation used to refer to a particular launch vehicle family.
-
C.
launchVehicleUser
Indicates that one entity uses or operates a particular launch vehicle to carry out a launch or space mission.
-
D.
launchVehicleType
Indicates the type or category of launch vehicle used to carry a payload or mission into space.
-
E.
launchVehicle
chosen
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be3cbe8c8190ba216eeebfc3cbec |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.