Triple
T30574186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сатин |
E778197
|
entity |
| Predicate | конфликтСПерсонажем |
P1406
|
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.
conflictRole
Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
-
B.
protagonistConfronts
Indicates that a main character directly faces and challenges another character, force, or problem in a conflictual encounter.
-
C.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
D.
conflictIn
chosen
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
E.
storyConflict
Indicates a relationship where a story contains or centers around a central problem, opposition, or tension that drives its plot.
- 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_69f689167878819093cb4f58efd47e2e |
completed | May 2, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:22 p.m.