Triple
T35589406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voskhod 2 |
E1028450
|
entity |
| Predicate | missionLanguage |
P56541
|
FINISHED |
| Object | Russian |
—
|
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: Russian | Statement: [Voskhod 2, missionLanguage, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionLanguage Context triple: [Voskhod 2, missionLanguage, Russian]
-
A.
eligibleLanguage
Indicates that a particular language satisfies the required conditions to be considered valid or allowed in a given context.
-
B.
targetsLanguage
Indicates that an action, resource, or entity is specifically directed toward, designed for, or intended to be used with a particular language.
-
C.
targetLanguage
chosen
Indicates the language that is the intended recipient or focus of a communication, translation, or linguistic operation.
-
D.
possibleLanguage
Indicates that an entity could plausibly be expressed, interpreted, or communicated in a given language.
-
E.
officialLanguage
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:05 p.m.