Triple
T2016287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Chancellorsville |
E44000
|
entity |
| Predicate | jacksonWoundDate |
P27390
|
FINISHED |
| Object | 1863-05-02 |
—
|
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-05-02 | Statement: [Battle of Chancellorsville, jacksonWoundDate, 1863-05-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jacksonWoundDate Context triple: [Battle of Chancellorsville, jacksonWoundDate, 1863-05-02]
-
A.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
B.
wasWoundedIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or conflict.
-
C.
dateOfRehabilitation
Indicates the specific date on which a rehabilitation process, status, or measure for an entity was completed, granted, or took effect.
-
D.
dateOfTragedy
chosen
Indicates the specific calendar date on which a tragic event occurred.
-
E.
dateOfLoss
Indicates the specific date on which a loss event (such as damage, theft, or other covered incident) occurred.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8cb16048190bc626685fbb5f707 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.