Triple
T518264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinco de Mayo |
E10755
|
entity |
| Predicate | popularizedInUSDuring |
P2352
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Cinco de Mayo, popularizedInUSDuring, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularizedInUSDuring Context triple: [Cinco de Mayo, popularizedInUSDuring, 20th century]
-
A.
popularizedIn
chosen
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
B.
popularizedBy
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
-
C.
introducedDuring
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
D.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
E.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
- 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.