Triple
T36771953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essays of Hugh Boyle Ewing |
E908502
|
entity |
| Predicate | hasAuthorMilitaryConflict |
P180533
|
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: [Essays of Hugh Boyle Ewing, hasAuthorMilitaryConflict, American Civil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorMilitaryConflict Context triple: [Essays of Hugh Boyle Ewing, hasAuthorMilitaryConflict, American Civil War]
-
A.
hasAuthorMilitaryService
chosen
Indicates that the author has served in the military or armed forces.
-
B.
conflictExperience
Indicates that an entity has undergone or been involved in a conflict, such as a dispute, struggle, or confrontation.
-
C.
militaryConflictInBackstory
Indicates that a character or entity has a history involving a military conflict that occurred prior to the main events or timeline being described.
-
D.
hadMilitaryFollowing
Indicates that an entity was supported or backed by a group of military personnel or forces.
-
E.
hasMonthOfConflict
Indicates that a conflict is associated with, occurs in, or is characterized by a specific calendar month.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:12 p.m.