Triple
T2995797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundance Film Festival Special Jury Award for Best Actor (for Jockey) |
E81062
|
entity |
| Predicate | isSpecialJuryHonor |
P44900
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sundance Film Festival Special Jury Award for Best Actor (for Jockey), isSpecialJuryHonor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpecialJuryHonor Context triple: [Sundance Film Festival Special Jury Award for Best Actor (for Jockey), isSpecialJuryHonor, true]
-
A.
hasJuryType
Indicates that an entity is associated with, or classified by, a specific type or category of jury.
-
B.
notableJuryMember
Indicates that an entity served as a distinguished or noteworthy member of a particular jury or judging panel.
-
C.
usesJuries
Indicates that a legal system, court, or process employs juries to participate in deciding cases or determining outcomes.
-
D.
juryProvidedBy
Indicates that a particular jury is supplied, appointed, or made available by a specified source or authority.
-
E.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
- F. None of above. chosen
Provenance (4 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f481688190ae8cd1e057f9dfc7 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 2:59 p.m.