Triple
T27862177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romaria de Finados |
E704257
|
entity |
| Predicate | observedOnOrAround |
P39845
|
FINISHED |
| Object | Dia de Finados |
—
|
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: Dia de Finados | Statement: [Romaria de Finados, observedOnOrAround, Dia de Finados]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedOnOrAround Context triple: [Romaria de Finados, observedOnOrAround, Dia de Finados]
-
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.
observedWhen
Indicates that one entity is observed or recorded at a specific time or under particular temporal conditions.
-
C.
observedAt
Indicates that an entity was recorded or noticed at a specific time or place.
-
D.
alsoObservedOn
Indicates that the same entity, event, or phenomenon was additionally observed on another occasion, date, or context beyond the primary one referenced.
-
E.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 6:18 p.m.