Triple
T266520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copa América Centenario 2016 matches |
E5741
|
entity |
| Predicate | anniversary |
P6046
|
FINISHED |
| Object | 100th anniversary of Copa América |
—
|
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: 100th anniversary of Copa América | Statement: [Copa América Centenario 2016 matches, anniversary, 100th anniversary of Copa América]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anniversary Context triple: [Copa América Centenario 2016 matches, anniversary, 100th anniversary of Copa América]
-
A.
typeOfAnniversary
chosen
Indicates the specific category or kind of anniversary that an event or date represents (e.g., wedding, work, founding).
-
B.
completionAnniversary
Indicates the date or event marking the anniversary of when something was originally completed.
-
C.
announcementOccasion
Indicates the specific event, context, or circumstance on the basis of which an announcement is made.
-
D.
year
Indicates the specific calendar year associated with an entity, event, or fact.
-
E.
annualFrom
Indicates that something recurs or is calculated on a yearly basis starting from a specified point in time.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d90bab48190b3ef97a451653b7f |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6f60b081908fc6467800a8849e |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.