Triple
T21597691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Jury Prize (Karlovy Vary IFF) |
E532944
|
entity |
| Predicate | hasPhysicalTrophy |
P28247
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Special Jury Prize (Karlovy Vary IFF), hasPhysicalTrophy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalTrophy Context triple: [Special Jury Prize (Karlovy Vary IFF), hasPhysicalTrophy, yes]
-
A.
hasTrophyStatus
Indicates that an entity possesses a particular trophy-related status or classification.
-
B.
hasTrophyForm
Indicates that one entity exists in, or is characterized by, a special trophy-like form or version of another entity.
-
C.
trophy
Indicates that one entity is a trophy awarded or possessed in relation to another entity, typically as a result of winning or achieving something.
-
D.
trophyWonWith
Indicates that a particular trophy or award was achieved using, through, or in association with a specified means, tool, team, or context.
-
E.
hasRelatedTrophy
chosen
Indicates that there exists a trophy that is associated with, linked to, or relevant to the given entity.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefae2fc908190b989f39e8cefffb2 |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:32 p.m.