Triple
T13025111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Andrés Mixquic |
E326283
|
entity |
| Predicate | usesTraditionalDecoration |
P107519
|
FINISHED |
| Object | papel picado |
—
|
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: papel picado | Statement: [San Andrés Mixquic, usesTraditionalDecoration, papel picado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTraditionalDecoration Context triple: [San Andrés Mixquic, usesTraditionalDecoration, papel picado]
-
A.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
B.
traditionalStyle
Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
-
C.
hasTraditionalColors
Indicates that an entity is associated with colors that are traditionally or customarily linked to it.
-
D.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
-
E.
settingTraditional
Indicates that something is situated or occurs within a traditional setting, context, or environment.
- 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_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. |
| PDg | Predicate description generation | batch_69d97e3df2288190a7f27d31d248bb7f |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:53 p.m.