Triple
T29472335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Белое солнце пустыни |
E747543
|
entity |
| Predicate | главныйГерой |
P9202
|
FINISHED |
| Object | Фёдор Сухов |
—
|
NE NERFINISHED |
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.
mainProtagonist
chosen
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
B.
nativeHero
Indicates that an entity is regarded as a heroic figure originating from or strongly associated with a particular place or community.
-
C.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
D.
baseHero
Indicates that one entity serves as the primary or foundational hero associated with another entity.
-
E.
mainMortalCharacter
Indicates that the referenced entity serves as the primary mortal (non-immortal) character in the context of a story or narrative.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 3:58 p.m.