Triple
T13025102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Andrés Mixquic |
E326283
|
entity |
| Predicate | hasTraditionalEventDate |
P88891
|
FINISHED |
| Object | 1 November |
—
|
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: 1 November | Statement: [San Andrés Mixquic, hasTraditionalEventDate, 1 November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalEventDate Context triple: [San Andrés Mixquic, hasTraditionalEventDate, 1 November]
-
A.
traditionallyDated
Indicates that something is assigned a date based on traditional or customary chronology rather than on firmly established historical or scientific evidence.
-
B.
hasTraditionalOriginEvent
Indicates that something originates from, or is derived from, a specific traditional event or customary practice.
-
C.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
D.
majorFestivalDate
chosen
Indicates the calendar date on which a major festival or significant celebratory event takes place.
-
E.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efac71881908a21d70c3c6ce099 |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:53 p.m.