Triple
T10691946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 19 |
E252031
|
entity |
| Predicate | languageOfRadioCommunications |
P33549
|
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: [Soyuz 19, languageOfRadioCommunications, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfRadioCommunications Context triple: [Soyuz 19, languageOfRadioCommunications, Russian]
-
A.
combatantLanguage
Indicates the language used by a combatant in a conflict or competitive interaction.
-
B.
languageOfCommunications
chosen
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
C.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
D.
isWorkingLanguageOf
Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
-
E.
languageOfTransmission
Indicates the language used to convey or transmit the content or information in a given communication or resource.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd37cf408190a1912b3e0aa096a5 |
completed | April 9, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:11 p.m.