Triple
T35604250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1988 Cannes Film Festival (out of competition) |
E1028840
|
entity |
| Predicate | screeningStatus |
P9177
|
FINISHED |
| Object | out of competition |
—
|
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: out of competition | Statement: [1988 Cannes Film Festival (out of competition), screeningStatus, out of competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screeningStatus Context triple: [1988 Cannes Film Festival (out of competition), screeningStatus, out of competition]
-
A.
screeningOutcome
Indicates the result or decision produced by a screening or evaluation process applied to an entity.
-
B.
screeningType
chosen
Indicates the specific method or category of screening applied in a screening process or evaluation.
-
C.
hasScreening
Indicates that one entity conducts, hosts, or is associated with a particular screening event involving another entity.
-
D.
screenedWith
Indicates that one entity is examined, tested, or evaluated using another entity as the screening method, tool, or criterion.
-
E.
screenedOn
Indicates that something (such as a film, show, or content) was shown or broadcast on a particular screen, channel, platform, or date.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.