Triple
T4255927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Lorenzo Acopilco |
E95973
|
entity |
| Predicate | hasCulturalCharacter |
P20656
|
FINISHED |
| Object | traditional |
—
|
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: traditional | Statement: [San Lorenzo Acopilco, hasCulturalCharacter, traditional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalCharacter Context triple: [San Lorenzo Acopilco, hasCulturalCharacter, traditional]
-
A.
hasCulturalFeature
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
B.
hasCulturalExpression
Indicates that an entity embodies, manifests, or is associated with a particular cultural form, practice, or expression.
-
C.
hasCulturalSignificance
Indicates that something holds notable meaning, value, or importance within a particular culture or cultural context.
-
D.
hasCulturalIcon
Indicates that an entity is associated with or possesses a person, symbol, or object widely recognized as a significant representation of a particular culture.
-
E.
hasCulturalProperty
chosen
Indicates that something possesses or is associated with a cultural attribute, value, or characteristic.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ec1971c81908f7a72418efa8bcc |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.