Triple
T23929329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James B. McPherson Memorial |
E602447
|
entity |
| Predicate | subjectHasConflict |
P107409
|
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: [James B. McPherson Memorial, subjectHasConflict, American Civil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectHasConflict Context triple: [James B. McPherson Memorial, subjectHasConflict, American Civil War]
-
A.
subjectConflict
Indicates that there is a disagreement, clash, or opposing stance between the subject and another party or situation.
-
B.
subConflict
Indicates that one conflict is a component, phase, or subordinate part of a larger overarching conflict.
-
C.
mentionsConflict
Indicates that one entity refers to or discusses a dispute, disagreement, or conflict involving another entity.
-
D.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
E.
hasSubjectConflictParticipatedIn
chosen
Indicates that a subject is involved in or has taken part in a particular conflict.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf9a18248190b20991969921ecfd |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:55 p.m.