Triple
T18031403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relief of Derry day |
E431397
|
entity |
| Predicate | historicalEventYearCommemorated |
P13724
|
FINISHED |
| Object | 1689 |
—
|
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: 1689 | Statement: [Relief of Derry day, historicalEventYearCommemorated, 1689]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEventYearCommemorated Context triple: [Relief of Derry day, historicalEventYearCommemorated, 1689]
-
A.
commemoratedYear
chosen
Indicates the specific year in which an event, person, or entity is formally remembered, honored, or celebrated.
-
B.
hasHistoricEventYear
Indicates the specific year in which a referenced historic event took place.
-
C.
timeOfEventCommemorated
Indicates the specific time or date at which the event being commemorated originally occurred.
-
D.
periodCommemorated
Indicates that something serves to honor, remember, or mark a specific historical or temporal period.
-
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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be35a70081909d24d36506d18131 |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.