Triple
T668087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Prix (Cannes Film Festival) |
E12909
|
entity |
| Predicate | hasAwardLevel |
P18108
|
FINISHED |
| Object | grand prize of the jury |
—
|
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: grand prize of the jury | Statement: [Grand Prix (Cannes Film Festival), hasAwardLevel, grand prize of the jury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAwardLevel Context triple: [Grand Prix (Cannes Film Festival), hasAwardLevel, grand prize of the jury]
-
A.
hasAwarded
Indicates that one entity has given or conferred an award to another entity.
-
B.
canAward
Indicates that one entity has the authority or ability to grant an award, honor, or recognition to another entity.
-
C.
hasSubsequentAward
Indicates that an entity has received an additional award that follows a previous award in time or sequence.
-
D.
hasAwardedDiscipline
Indicates that one entity has formally imposed or granted a disciplinary action or sanction upon another entity.
-
E.
awardStatus
Indicates the current state or outcome of an award in relation to an entity, such as whether it has been granted, pending, rejected, or completed.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ff921288190a2e5edb201ba69ee |
completed | March 1, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69a49d18942c819083b3d1887e505900 |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49fcf0cb4819096edea4037ca2c03 |
completed | March 1, 2026, 8:21 p.m. |
Created at: March 1, 2026, 7:36 p.m.