Triple
T32769049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gagarin's Start |
E837982
|
entity |
| Predicate | firstLaunchVehicleFamily |
P111750
|
FINISHED |
| Object | R-7 Semyorka |
E62034
|
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: R-7 Semyorka | Statement: [Gagarin's Start, firstLaunchVehicleFamily, R-7 Semyorka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLaunchVehicleFamily Context triple: [Gagarin's Start, firstLaunchVehicleFamily, R-7 Semyorka]
-
A.
primaryLaunchVehicleType
Indicates the type or category of launch vehicle that is primarily used to carry a payload into space.
-
B.
firstFlightLaunchVehicle
Indicates that the subject is the launch vehicle used for an entity’s first flight.
-
C.
firstSuccessfulOrbitalLaunchVehicle
Indicates that the subject is the launch vehicle that achieved the first successful orbital launch for the associated space program, organization, or country.
-
D.
usedOnLaunchVehicleFamily
Indicates that something (such as a component, system, or technology) is employed or implemented on a particular family of launch vehicles.
-
E.
firstLaunchedRocketType
chosen
Indicates the type or model of the first rocket that was launched in a given context or by a given entity.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34bce943c48190a405bb7e9d9ae280 |
completed | June 19, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:13 a.m.