Triple
T29998567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RD-171 |
E762097
|
entity |
| Predicate | usedOnRocketFamily |
P96565
|
FINISHED |
| Object | Zenit family |
—
|
NE NERFINISHED |
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: Zenit family | Statement: [RD-171, usedOnRocketFamily, Zenit family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnRocketFamily Context triple: [RD-171, usedOnRocketFamily, Zenit family]
-
A.
usedOnLaunchVehicleFamily
chosen
Indicates that something (such as a component, system, or technology) is employed or implemented on a particular family of launch vehicles.
-
B.
usedInRocket
Indicates that something is employed as a component, material, or subsystem within a rocket or its operation.
-
C.
associatedRocketFamily
Indicates that one entity is related to or belongs to the same rocket family or rocket lineage as another entity.
-
D.
usedByRocket
Indicates that something serves as a component, resource, or tool that is utilized by a rocket.
-
E.
usedOnLaunchVehicleVariant
Indicates that something (such as a component, system, or configuration) is employed on a specific variant of a launch vehicle.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6794cf5848190a60ca2c4d9f50098 |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:40 p.m.