Triple
T29472245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Джентльмены удачи |
E747539
|
entity |
| Predicate | целевой зритель |
P10804
|
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.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
B.
broaderTarget
Indicates that one target concept encompasses or is more general than another, defining a broader-to-narrower target relationship.
-
C.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
D.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
-
E.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
- 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_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:58 p.m.