Triple
T3979831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannes closing ceremony |
E85729
|
entity |
| Predicate | eventSequence |
P4074
|
FINISHED |
| Object | final event of the 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: final event of the Cannes Film Festival | Statement: [Cannes closing ceremony, eventSequence, final event of the Cannes Film Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventSequence Context triple: [Cannes closing ceremony, eventSequence, final event of the Cannes Film Festival]
-
A.
partOfSeriesOfEvents
chosen
Indicates that an event is one element within a larger, ordered sequence of related events.
-
B.
eventContext
Indicates the situational or background circumstances (such as time, place, conditions, or surrounding events) within which a particular event occurs or is interpreted.
-
C.
eventCommanded
Indicates that one entity issued an order or directive for another entity to carry out a specific event or action.
-
D.
featuresSequence
Indicates that one entity presents or contains another entity as an ordered sequence of features or elements.
-
E.
eventUsage
Indicates how an event is employed, applied, or utilized within a particular context or process.
- 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa3ef7ac8190abe02f440ff83c43 |
completed | March 9, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69aef8f492ac819089dbb9436dbcdd2b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.