Triple
T10691918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 19 |
E252031
|
entity |
| Predicate | launchSite |
P4384
|
FINISHED |
| Object | Baikonur Cosmodrome |
E40639
|
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: Baikonur Cosmodrome | Statement: [Soyuz 19, launchSite, Baikonur Cosmodrome]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Baikonur Cosmodrome Context triple: [Soyuz 19, launchSite, Baikonur Cosmodrome]
-
A.
Baikonur Cosmodrome
chosen
Baikonur Cosmodrome is the historic Soviet and now Russian-operated spaceport in Kazakhstan from which the first human spaceflight, carrying Yuri Gagarin, was launched.
-
B.
Baikonur
Baikonur is a town in Kazakhstan historically associated with the Soviet and Russian space programs, giving its name to the nearby Baikonur Cosmodrome.
-
C.
Baikonur
Baikonur is a metro station on the Almaty Metro system in Almaty, Kazakhstan.
-
D.
Vostochny Cosmodrome
Vostochny Cosmodrome is a Russian spaceport in the Amur Oblast designed to reduce Russia’s dependence on the Baikonur Cosmodrome in Kazakhstan and support a wide range of civilian space launches.
-
E.
Plesetsk Cosmodrome
Plesetsk Cosmodrome is a major Russian spaceport in the Arkhangelsk region primarily used for military and polar-orbit satellite launches.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd37cf408190a1912b3e0aa096a5 |
completed | April 9, 2026, 1:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d988ad741c8190b9ae962e0c5bc272 |
completed | April 10, 2026, 11:33 p.m. |
Created at: April 8, 2026, 9:11 p.m.