Triple
T35075337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voskhod 1 |
E1011995
|
entity |
| Predicate | languageOfMissionName |
P15
|
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 1, languageOfMissionName, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfMissionName Context triple: [Voskhod 1, languageOfMissionName, Russian]
-
A.
hasLanguageOfMission
Indicates that an entity (such as a mission or project) is associated with a specific language used for its communication, documentation, or operation.
-
B.
originalNameOfMission
Indicates the original or initial name that was assigned to a mission before any renaming or reclassification.
-
C.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
D.
languageOfWorkOrName
chosen
Indicates the language in which a work is created or a name is expressed.
-
E.
missionNameMeaning
Indicates that one entity specifies or explains the meaning or significance of the name of a mission associated with another entity.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.