Triple
T11441134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiestas del Pilar |
E271144
|
entity |
| Predicate | aroundDate |
P39845
|
FINISHED |
| Object | 12 October |
—
|
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: 12 October | Statement: [Fiestas del Pilar, aroundDate, 12 October]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aroundDate Context triple: [Fiestas del Pilar, aroundDate, 12 October]
-
A.
occursOnOrAround
chosen
Indicates that an event or action takes place on a specific date or within a small, approximate time window surrounding that date.
-
B.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
around
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
-
E.
associatedWorkDate
Indicates the date on which a related or associated work (such as a publication, performance, or creation) is linked to the subject entity.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d80888190c8190b6365550ffe4931c |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.