Triple
T31904355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centennial of the Mexican Revolution (2010) |
E814507
|
entity |
| Predicate | mainCommemorativeDate |
P865
|
FINISHED |
| Object | 2010-11-20 |
—
|
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: 2010-11-20 | Statement: [Centennial of the Mexican Revolution (2010), mainCommemorativeDate, 2010-11-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCommemorativeDate Context triple: [Centennial of the Mexican Revolution (2010), mainCommemorativeDate, 2010-11-20]
-
A.
commemorationDate
Indicates the date on which an event, person, or occasion is formally remembered or honored.
-
B.
periodCommemorated
Indicates that something serves to honor, remember, or mark a specific historical or temporal period.
-
C.
commemoratedOn
chosen
Indicates that something is remembered, honored, or celebrated on a specific date or occasion.
-
D.
currentCommemoration
Indicates that an entity is the subject of a commemoration event or observance that is presently taking place or being recognized.
-
E.
commemoratesEventOn
Indicates that one entity marks, honors, or observes a specific event on a particular date or occasion.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, midnight