Triple
T38298748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbine Memorial in Clement Park |
E1032164
|
entity |
| Predicate | memorializesEventDate |
P18981
|
FINISHED |
| Object | April 20, 1999 |
—
|
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: April 20, 1999 | Statement: [Columbine Memorial in Clement Park, memorializesEventDate, April 20, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memorializesEventDate Context triple: [Columbine Memorial in Clement Park, memorializesEventDate, April 20, 1999]
-
A.
commemoratesEventOn
Indicates that one entity marks, honors, or observes a specific event on a particular date or occasion.
-
B.
commemorationDate
Indicates the date on which an event, person, or occasion is formally remembered or honored.
-
C.
commemoratedOn
Indicates that something is remembered, honored, or celebrated on a specific date or occasion.
-
D.
timeOfEventCommemorated
chosen
Indicates the specific time or date at which the event being commemorated originally occurred.
-
E.
commemoratesEventWith
Indicates that one entity serves as a memorial or tribute to a specific event, marking or honoring its occurrence.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.