Triple
T35788130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival de Cannes organizing committee |
E1034617
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governing body of cultural event |
C172
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: governing body of cultural event Context triple: [Festival de Cannes organizing committee, instanceOf, governing body of cultural event]
-
A.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
B.
cultural event
A cultural event is a planned gathering or activity that showcases, celebrates, or transmits the traditions, arts, values, or practices of a particular community or society.
-
C.
festival organization
Festival organization is the coordinated planning, management, and execution of all logistical, financial, promotional, and experiential aspects required to design and deliver a successful festival event.
-
D.
cultural institution
A cultural institution is an organized establishment, such as a museum, library, theater, or gallery, dedicated to preserving, interpreting, and promoting the arts, heritage, and shared cultural expressions of a community or society.
-
E.
fair organizing body
A fair organizing body is an entity responsible for planning, coordinating, and overseeing the operations, logistics, and governance of a fair or exhibition to ensure it runs smoothly, safely, and in accordance with relevant regulations and objectives.
- F. None of above.
Provenance (1 batch)
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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.