Triple
T33347465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Jury Prize |
E853837
|
entity |
| Predicate | isCommunicatedDuring |
P180676
|
FINISHED |
| Object | festival awards ceremony |
—
|
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: festival awards ceremony | Statement: [Special Jury Prize, isCommunicatedDuring, festival awards ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommunicatedDuring Context triple: [Special Jury Prize, isCommunicatedDuring, festival awards ceremony]
-
A.
communicatedOn
Indicates that a communication event took place on a specific date or time.
-
B.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
C.
hasCommunicationType
Indicates that one entity uses, supports, or is associated with a particular form or mode of communication.
-
D.
hasCommunicationAccess
Indicates that one entity is able to communicate with, or use a communication channel or service provided by, another entity.
-
E.
hasCommunicationUse
Indicates that something is used for, or serves the purpose of, communication.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: May 1, 2026, 1:34 a.m.