Triple
T17975318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bicentennial of Chile |
E449453
|
entity |
| Predicate | historicalStartingEventDate |
P72902
|
FINISHED |
| Object | 1810-09-18 |
—
|
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: 1810-09-18 | Statement: [Bicentennial of Chile, historicalStartingEventDate, 1810-09-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalStartingEventDate Context triple: [Bicentennial of Chile, historicalStartingEventDate, 1810-09-18]
-
A.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
B.
chronologyStartEvent
chosen
Indicates the event that marks the beginning or initial point in a chronological sequence or timeline.
-
C.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
D.
nearHistoricalEventDate
Indicates that something occurs on a date that is close in time to a specified historical event’s date.
-
E.
hasHistoricEventYear
Indicates the specific year in which a referenced historic event took place.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b1fee86c8190a9a220b008e78e10 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.