Triple
T25140180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stonewall of the West |
E629780
|
entity |
| Predicate | subjectWar |
P106867
|
FINISHED |
| Object | American Civil War |
—
|
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: American Civil War | Statement: [Stonewall of the West, subjectWar, American Civil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectWar Context triple: [Stonewall of the West, subjectWar, American Civil War]
-
A.
concernsWarBetween
chosen
Indicates a relationship where something (such as a statement, document, or event) is about or pertains to a war occurring between two or more parties.
-
B.
warName
Indicates the specific name or title assigned to a particular war or armed conflict.
-
C.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
-
D.
casusBelli
Indicates a relationship where one entity serves as the cause, justification, or pretext for another entity to initiate conflict or war.
-
E.
subsequentWar
Indicates that one war occurs after and as a consequence or continuation of another war.
- 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_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:29 a.m.