Triple
T35087556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blok D upper stage |
E1012617
|
entity |
| Predicate | usedWithLaunchSite |
P94508
|
FINISHED |
| Object | Baikonur Cosmodrome |
—
|
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: Baikonur Cosmodrome | Statement: [Blok D upper stage, usedWithLaunchSite, Baikonur Cosmodrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWithLaunchSite Context triple: [Blok D upper stage, usedWithLaunchSite, Baikonur Cosmodrome]
-
A.
usesLaunchSite
Indicates that an entity conducts or carries out its launches from a particular launch site.
-
B.
usesLaunchVehicleCore
Indicates that a space mission or launch event makes use of a specific launch vehicle core as part of its propulsion or structural stack.
-
C.
usedForLaunchOf
Indicates that something serves as the means, tool, or platform by which a launch (such as of a product, mission, or event) is carried out.
-
D.
servesLaunchSite
Indicates that one entity functions as the launch site used by another entity for initiating launches.
-
E.
usedByLaunchVehicle
chosen
Indicates that something (such as equipment, infrastructure, or a resource) is utilized by a specific launch vehicle during its operations.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.