Triple
T15527369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peñafiel |
E369116
|
entity |
| Predicate | traditionalEventLocation |
P17057
|
FINISHED |
| Object | bullfighting in Plaza del Coso |
—
|
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: bullfighting in Plaza del Coso | Statement: [Peñafiel, traditionalEventLocation, bullfighting in Plaza del Coso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalEventLocation Context triple: [Peñafiel, traditionalEventLocation, bullfighting in Plaza del Coso]
-
A.
traditionalMeetingPlace
Indicates that a location is customarily used as a gathering spot for meetings or social interactions according to established tradition.
-
B.
typicallyHeldIn
chosen
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
-
C.
eventLocationOfNotableActivity
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
-
D.
locationOfEventDescribed
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
E.
traditionalVenuePeriod
Indicates the time span during which a venue is used in its customary or historically established manner.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0414620588190958ffde651ccab5f |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:05 a.m.