Triple
T24308450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salavat Yulaev |
E612598
|
entity |
| Predicate | notableLanguageOfFanbase |
P3778
|
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: [Salavat Yulaev, notableLanguageOfFanbase, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLanguageOfFanbase Context triple: [Salavat Yulaev, notableLanguageOfFanbase, Russian]
-
A.
languageOfFanbase
chosen
Indicates the primary language or languages commonly used by a fanbase in its communication and expression.
-
B.
notableMemberLanguage
Indicates that the language is notably associated with or used by a prominent member of the referenced group or entity.
-
C.
notableFan
Indicates that one entity is a well-known or especially prominent admirer or supporter of another entity.
-
D.
languageOfClubHeritage
Indicates the language traditionally associated with or used to represent a club’s cultural or historical heritage.
-
E.
hasFanBaseFor
Indicates that an entity has a group of supporters or admirers specifically dedicated to another entity (such as a work, person, or brand).
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29228ede48190b05c85320f373155 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:32 a.m.