Triple
T518262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinco de Mayo |
E10755
|
entity |
| Predicate | culturalFocusInUS |
P7511
|
FINISHED |
| Object | Mexican heritage |
—
|
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: Mexican heritage | Statement: [Cinco de Mayo, culturalFocusInUS, Mexican heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalFocusInUS Context triple: [Cinco de Mayo, culturalFocusInUS, Mexican heritage]
-
A.
culturalSphere
Indicates that one entity belongs to, is influenced by, or participates in the cultural domain, tradition, or milieu defined by another entity.
-
B.
culturalMovement
Indicates that an entity is associated with, participates in, or belongs to a particular cultural movement or trend.
-
C.
culturalExport
chosen
Indicates that something originating in one culture is transmitted, adopted, or influential in another culture or region.
-
D.
cultureDepicted
Indicates that one entity portrays, represents, or is associated with the culture of another entity.
-
E.
culturalRegion
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f19ee6748190916603ef3a9e27f3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.