Triple
T9046408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannes Jury Prize |
E216765
|
entity |
| Predicate | morePrestigiousThan |
P86062
|
FINISHED |
| Object | Best Director Award at Cannes Film Festival |
—
|
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: Best Director Award at Cannes Film Festival | Statement: [Cannes Jury Prize, morePrestigiousThan, Best Director Award at Cannes Film Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: morePrestigiousThan Context triple: [Cannes Jury Prize, morePrestigiousThan, Best Director Award at Cannes Film Festival]
-
A.
isHighlyPrized
Indicates that something is regarded with exceptional value, admiration, or importance, often being especially sought after or cherished.
-
B.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
C.
moreExpensiveThan
Indicates that one entity has a higher cost or price than another entity.
-
D.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
E.
moreExpressiveThan
Indicates that one entity conveys ideas, emotions, or information with greater richness, nuance, or clarity than another.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b4e4b888190a425e29b193b506f |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f4f1cb48190a025d1b3d8d7a790 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:09 p.m.