Triple
T29472215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Джентльмены удачи |
E747539
|
entity |
| Predicate | главная роль |
P14496
|
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.
principalRoleIn
Indicates that an entity holds the primary or leading role in a particular context, activity, or relationship.
-
B.
hasMainRole
chosen
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
C.
primaryActor
Indicates that the referenced entity is the main participant or most central party responsible for the action or event in the relationship.
-
D.
peakRole
Indicates the role or position an entity holds at the highest or most prominent point of its activity, status, or performance.
-
E.
laterPrimaryRole
Indicates that an entity assumes a specified primary role at a later time than another role or state in a sequence.
- 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_69f66babf5e08190b8e1007546f3881a |
completed | May 2, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:58 p.m.