Triple
T9691379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klim Samgin |
E234543
|
entity |
| Predicate | characterInLanguage |
P12208
|
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: [Klim Samgin, characterInLanguage, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterInLanguage Context triple: [Klim Samgin, characterInLanguage, Russian]
-
A.
isCharacterInWorkLanguage
Indicates that a character appears in a work (e.g., book, film, game) in a specific language version or localization.
-
B.
characterIn
chosen
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
C.
characterCorrespondsTo
Indicates that one character is equivalent to, maps onto, or represents another character in a defined correspondence or mapping.
-
D.
languageOfLetters
Indicates that one entity is the language in which the other entity’s letters or written correspondence are composed.
-
E.
character3
Indicates a tertiary or additional character role associated with an entity, typically the third distinct character linked within a given context or work.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d0422e88190a234ba74eb0dad25 |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.