Triple
T31683376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buñol Town Council |
E808592
|
entity |
| Predicate | festivalTypeOrganized |
P91710
|
FINISHED |
| Object | tomato-throwing 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: tomato-throwing festival | Statement: [Buñol Town Council, festivalTypeOrganized, tomato-throwing festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalTypeOrganized Context triple: [Buñol Town Council, festivalTypeOrganized, tomato-throwing festival]
-
A.
festivalTypeHosted
chosen
Indicates that a particular location or organizer hosts festivals of a specified type.
-
B.
festivalOrganiser
Indicates that one entity is responsible for planning, coordinating, or managing a festival for another entity or context.
-
C.
festivalSystem
Indicates a relationship where an entity is part of, managed by, or associated with a festival-related organizational or operational system.
-
D.
festivalActivity
Indicates that an entity is an event, performance, or engagement that takes place as part of a festival’s organized program.
-
E.
festivalFunction
Indicates that an event serves as a festival or is functioning in the role of a festival within a given context.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:05 p.m.