Triple
T27263664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silletero procession |
E687838
|
entity |
| Predicate | centralEventOf |
P49138
|
FINISHED |
| Object | Feria de las Flores |
—
|
NE NERFINISHED |
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: Feria de las Flores | Statement: [Silletero procession, centralEventOf, Feria de las Flores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralEventOf Context triple: [Silletero procession, centralEventOf, Feria de las Flores]
-
A.
centralEventOfPiety
Indicates that an event serves as the primary or focal act of religious devotion or pious practice within a given context.
-
B.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
C.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
D.
centralEntity
Indicates that the subject serves as the primary or most important entity around which related entities, actions, or information are organized.
-
E.
mainEventFor
chosen
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
- 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 10:54 a.m.