Triple
T19983652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Presentations |
E493880
|
entity |
| Predicate | festivalSectionRole |
P35474
|
FINISHED |
| Object | showcase of major titles |
—
|
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: showcase of major titles | Statement: [Special Presentations, festivalSectionRole, showcase of major titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalSectionRole Context triple: [Special Presentations, festivalSectionRole, showcase of major titles]
-
A.
festivalOrganiser
Indicates that one entity is responsible for planning, coordinating, or managing a festival for another entity or context.
-
B.
positionInFestival
chosen
Indicates the specific role, slot, or placement an entity holds within the structure or schedule of a festival.
-
C.
festivalPresence
Indicates that an entity is present at, participates in, or is associated with a particular festival event.
-
D.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
E.
festivalSystem
Indicates a relationship where an entity is part of, managed by, or associated with a festival-related organizational or operational system.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d157d088190af861608936e59b7 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:28 p.m.