Triple
T284274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grito de Independencia |
E5854
|
entity |
| Predicate | relatedHistoricalDate |
P925
|
FINISHED |
| Object | September 16, 1810 |
—
|
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: September 16, 1810 | Statement: [Grito de Independencia, relatedHistoricalDate, September 16, 1810]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedHistoricalDate Context triple: [Grito de Independencia, relatedHistoricalDate, September 16, 1810]
-
A.
notableEventDate
chosen
Indicates the date on which a notable or significant event associated with the subject occurred.
-
B.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
C.
historicalMovementAssociatedWith
Indicates that there is an association between an entity and a historical movement, such as a social, political, cultural, or ideological current in history.
-
D.
commemorationDate
Indicates the date on which an event, person, or occasion is formally remembered or honored.
-
E.
historicEventAlsoKnownAs
Indicates that a historic event is referred to by an alternative name or alias.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e0d789881908d6a9a8d6a0d4a6c |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b795a6c8190944d48e8418e0ccd |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.