Triple
T25140181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stonewall of the West |
E629780
|
entity |
| Predicate | subjectNotableBattlefield |
P108382
|
FINISHED |
| Object | Battle of Shiloh |
—
|
NE NERFINISHED |
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: Battle of Shiloh | Statement: [Stonewall of the West, subjectNotableBattlefield, Battle of Shiloh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectNotableBattlefield Context triple: [Stonewall of the West, subjectNotableBattlefield, Battle of Shiloh]
-
A.
notableBattlefield
Indicates that a location is recognized as the site of a historically significant battle or military engagement.
-
B.
regionOfBattlesCommemorated
Indicates the geographic region where the battles being commemorated took place.
-
C.
notableBattleRecognized
chosen
Indicates that a particular battle is formally acknowledged or recognized as notable in relation to the subject.
-
D.
primaryBattlefieldOf
Indicates that a specified location serves as the main or most significant battlefield where a particular conflict or war primarily took place.
-
E.
battleSignificanceAtLocation
Indicates the degree of importance or impact that a particular battle has at a specified location.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 6:29 a.m.