Triple
T30574182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сатин |
E778197
|
entity |
| Predicate | странаПроисхожденияПерсонажа |
P34184
|
FINISHED |
| Object | Россия (литературный контекст) |
—
|
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: Россия (литературный контекст) | Statement: [Сатин, странаПроисхожденияПерсонажа, Россия (литературный контекст)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: странаПроисхожденияПерсонажа Context triple: [Сатин, странаПроисхожденияПерсонажа, Россия (литературный контекст)]
-
A.
originOfCharacter
Indicates the source or place from which a character originates or is created.
-
B.
characterOrigin
chosen
Indicates the source, background, or initial context from which a character originates.
-
C.
protagonistOrigin
Indicates that one entity is the origin, source, or starting point of the protagonist in a narrative or story.
-
D.
characterNameOrigin
Indicates the source or inspiration from which a character’s name is derived.
-
E.
aboutFictionalCharacter
Indicates that something (such as a work, statement, or discussion) concerns or is centered on a fictional character.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:22 p.m.