Triple
T10453526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bright Star |
E246491
|
entity |
| Predicate | sectionScreened |
P28181
|
FINISHED |
| Object | Competition at 2009 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: Competition at 2009 Cannes Film Festival | Statement: [Bright Star, sectionScreened, Competition at 2009 Cannes Film Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionScreened Context triple: [Bright Star, sectionScreened, Competition at 2009 Cannes Film Festival]
-
A.
hasScreened
chosen
Indicates that one entity has shown, displayed, or evaluated another entity, typically in the context of presenting media or conducting a review or check.
-
B.
screeningOutcome
Indicates the result or decision produced by a screening or evaluation process applied to an entity.
-
C.
screeningType
Indicates the specific method or category of screening applied in a screening process or evaluation.
-
D.
screeningBasis
Indicates the underlying reason, criterion, or grounds on which a screening or evaluation is conducted between entities.
-
E.
hasSecurityScreening
Indicates that an entity is subject to, or has undergone, a security screening 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe0d73d48190acb687b96918e0cf |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:17 p.m.