Triple
T5595793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molniya-M |
E146993
|
entity |
| Predicate | rocketFamilyRole |
P7205
|
FINISHED |
| Object | specialized variant for Molniya orbits |
—
|
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: specialized variant for Molniya orbits | Statement: [Molniya-M, rocketFamilyRole, specialized variant for Molniya orbits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rocketFamilyRole Context triple: [Molniya-M, rocketFamilyRole, specialized variant for Molniya orbits]
-
A.
familyOrganizerRole
Indicates the specific role or capacity an individual holds as the organizer or manager within a family group or household.
-
B.
enemyFamily
Indicates that two entities belong to families that are hostile or in conflict with each other.
-
C.
associatedRocketFamily
Indicates that one entity is related to or belongs to the same rocket family or rocket lineage as another entity.
-
D.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
E.
relatedRocketFamily
chosen
Indicates that two rockets are members of the same rocket family or closely related rocket variants.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020be029881908c5586838382c8f2 |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.