Triple
T26801227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnival of Riosucio |
E671106
|
entity |
| Predicate | celebratedEvery |
P161240
|
FINISHED |
| Object | two years |
—
|
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: two years | Statement: [Carnival of Riosucio, celebratedEvery, two years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celebratedEvery Context triple: [Carnival of Riosucio, celebratedEvery, two years]
-
A.
celebratedThrough
Indicates that something is honored, recognized, or observed by means of a particular activity, medium, or practice.
-
B.
celebratedDuring
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
-
C.
celebratedAs
Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
-
D.
celebratedAfter
Indicates that one event or celebration occurs later in time as a result of, or in response to, another specified event.
-
E.
celebratedAt
Indicates that an event, occasion, or achievement is celebrated or observed at a particular place or time.
- F. None of above. chosen
Provenance (4 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 4:23 a.m.