Triple
T15486288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Averasborough |
E377055
|
entity |
| Predicate | stateOfWar |
P88699
|
FINISHED |
| Object | late stage of the American Civil War |
—
|
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: late stage of the American Civil War | Statement: [Battle of Averasborough, stateOfWar, late stage of the American Civil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOfWar Context triple: [Battle of Averasborough, stateOfWar, late stage of the American Civil War]
-
A.
warStatus
chosen
Indicates the state or condition of conflict or war that exists between entities at a given time.
-
B.
warName
Indicates the specific name or title assigned to a particular war or armed conflict.
-
C.
stateDuringWar
Indicates that a state or condition exists specifically in the context of, or for the duration of, a war or armed conflict.
-
D.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
-
E.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f8f71a08190a440ff19dcc65312 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:47 a.m.