Triple
T11791070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Kadooment |
E280385
|
entity |
| Predicate | roleInFestival |
P35474
|
FINISHED |
| Object | climax of Crop Over |
—
|
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: climax of Crop Over | Statement: [Grand Kadooment, roleInFestival, climax of Crop Over]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFestival Context triple: [Grand Kadooment, roleInFestival, climax of Crop Over]
-
A.
positionInFestival
chosen
Indicates the specific role, slot, or placement an entity holds within the structure or schedule of a festival.
-
B.
operatesFestival
Indicates that one entity manages and runs the organization or execution of a festival for another entity or in a particular context.
-
C.
workRoleInRocknRolla
Indicates the specific role or function an entity has within the context of the work "RocknRolla."
-
D.
organizerRole
Indicates that an entity has the role or responsibility of organizing an event, activity, or group.
-
E.
talentShowRole
Indicates the specific function or position an entity holds within the context of a talent show (e.g., performer, judge, host).
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a588d2c881909783c2d678c2a474 |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.