Triple
T1270826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Critics’ Week |
E15703
|
entity |
| Predicate | screeningVenueType |
P25526
|
FINISHED |
| Object | cinema theatres in Cannes |
—
|
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: cinema theatres in Cannes | Statement: [Critics’ Week, screeningVenueType, cinema theatres in Cannes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screeningVenueType Context triple: [Critics’ Week, screeningVenueType, cinema theatres in Cannes]
-
A.
screeningType
Indicates the specific method or category of screening applied in a screening process or evaluation.
-
B.
refersToVenueType
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
C.
theatreType
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
-
D.
hasEntertainmentVenue
Indicates that an entity possesses, contains, or is associated with an entertainment venue as part of its facilities or offerings.
-
E.
typicalVenues
chosen
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c06ae7b88190a1e0b5232d84a7b1 |
completed | March 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.