Triple
T2333837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley Campaign of 1862 |
E44264
|
entity |
| Predicate | dateOfLastBattle |
P20879
|
FINISHED |
| Object | 1862-06-09 |
—
|
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: 1862-06-09 | Statement: [Valley Campaign of 1862, dateOfLastBattle, 1862-06-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfLastBattle Context triple: [Valley Campaign of 1862, dateOfLastBattle, 1862-06-09]
-
A.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
B.
battleDateRelation
Indicates the temporal relationship specifying on which date a particular battle or combat event took place.
-
C.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
D.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
E.
battleEndDate
chosen
Indicates the date on which a specific battle or military engagement concluded.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6f75d888190a2e41edaa532e83f |
completed | March 7, 2026, 6:34 a.m. |
| PD | Predicate disambiguation | batch_69abc594087c819098100a10c5478a4b |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:51 p.m.