Triple
T36614521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 6 |
E903565
|
entity |
| Predicate | languageOfCallSign |
P84591
|
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 6, languageOfCallSign, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfCallSign Context triple: [Soyuz 6, languageOfCallSign, Russian]
-
A.
callsignLanguage
chosen
Indicates the language in which a callsign is expressed or encoded.
-
B.
callsign
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
C.
callsignOrDesignation
Indicates that one entity serves as the callsign or formal designation used to identify another entity in communication or operational contexts.
-
D.
icaoCallsignFor
Indicates that one entity is the ICAO-assigned callsign used in air traffic communications for the other entity (typically an airline or aircraft operator).
-
E.
callSignLanguage
Indicates that one entity communicates with another using sign language as the medium of the call or conversation.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a013c50bcb8819086d163f1a796a9b8 |
completed | May 11, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_6a013c01bac88190b15c70910c02a8a7 |
completed | May 11, 2026, 2:16 a.m. |
Created at: May 3, 2026, 4:11 p.m.