Triple
T518257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinco de Mayo |
E10755
|
entity |
| Predicate | significanceInMexico |
P12510
|
FINISHED |
| Object | regional holiday |
—
|
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: regional holiday | Statement: [Cinco de Mayo, significanceInMexico, regional holiday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significanceInMexico Context triple: [Cinco de Mayo, significanceInMexico, regional holiday]
-
A.
hasRegionalSignificance
chosen
Indicates that something holds particular importance, influence, or relevance within a specific geographic region.
-
B.
significance
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
-
C.
populationRankInMexico
Indicates the relative position of an entity in terms of population size compared to other entities within Mexico.
-
D.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
-
E.
isCulturalSignificance
Indicates that something holds notable meaning, value, or influence within a particular culture or cultural 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_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.