Triple
T19235000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jennie Wade House |
E480969
|
entity |
| Predicate | dateOfCivilianDeathOnPremises |
P76048
|
FINISHED |
| Object | 1863-07-03 |
—
|
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: 1863-07-03 | Statement: [Jennie Wade House, dateOfCivilianDeathOnPremises, 1863-07-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfCivilianDeathOnPremises Context triple: [Jennie Wade House, dateOfCivilianDeathOnPremises, 1863-07-03]
-
A.
dateOfTragedy
Indicates the specific calendar date on which a tragic event occurred.
-
B.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
C.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
D.
deathDateAtSite
chosen
Indicates the date on which an entity died at a specified location or site.
-
E.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faec6d0c8190b90cb1bb3160a847 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:26 p.m.