Triple
T36133490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Massacre at Fall Creek |
E1045089
|
entity |
| Predicate | historicalEventDateDepicted |
P126232
|
FINISHED |
| Object | 1824 |
—
|
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: 1824 | Statement: [The Massacre at Fall Creek, historicalEventDateDepicted, 1824]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEventDateDepicted Context triple: [The Massacre at Fall Creek, historicalEventDateDepicted, 1824]
-
A.
timeOfEventCommemorated
Indicates the specific time or date at which the event being commemorated originally occurred.
-
B.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
C.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
D.
dateDepicted
chosen
Indicates that one entity specifies the calendar date on which the other entity, typically an event or scene, is depicted as occurring.
-
E.
nearHistoricalEventDate
Indicates that something occurs on a date that is close in time to a specified historical event’s date.
- 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
Created at: May 3, 2026, 4:08 p.m.