Triple

T21597679
Position Surface form Disambiguated ID Type / Status
Subject Special Jury Prize (Karlovy Vary IFF) E532944 entity
Predicate hasJuryDecision P13938 FINISHED
Object collective decision 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: collective decision | Statement: [Special Jury Prize (Karlovy Vary IFF), hasJuryDecision, collective decision]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasJuryDecision
Context triple: [Special Jury Prize (Karlovy Vary IFF), hasJuryDecision, collective decision]
  • A. hasJudge
    Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
  • B. hasJurors
    Indicates that one entity serves as or includes jurors in relation to another entity, typically in the context of a legal case or proceeding.
  • C. hasJudges
    Indicates that one entity serves as a judge or panel of judges for another entity, such as an event, competition, or legal case.
  • D. hasFinalDecisionOn
    Indicates that one entity holds the ultimate authority or responsibility to make and enforce a conclusive decision regarding another entity or matter.
  • E. hasJuryType chosen
    Indicates that an entity is associated with, or classified by, a specific type or category of jury.
  • 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_69eefae20c8881909c5354313d06183a 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.