Triple
T22090741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chris Mannix |
E545904
|
entity |
| Predicate | politicalSideInCivilWar |
P58454
|
FINISHED |
| Object | Confederate |
—
|
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: Confederate | Statement: [Chris Mannix, politicalSideInCivilWar, Confederate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalSideInCivilWar Context triple: [Chris Mannix, politicalSideInCivilWar, Confederate]
-
A.
memberSupportedSideInCivilWar
chosen
Indicates that a member or group actively backed, aligned with, or provided support to a particular side or faction in a civil war.
-
B.
politicalSide
Indicates the political alignment or ideological position that one entity holds in relation to political spectra or groupings.
-
C.
opponentInAmericanCivilWar
Indicates that two entities were on opposing sides in the American Civil War.
-
D.
conflictSide
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
E.
hasCivilWarAssociation
Indicates a relationship in which an entity is connected or related to a civil war, such as through involvement, impact, or relevance.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e53dfc81909858cdad8b09c5fb |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.