Triple
T33811749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Yellow Bayou |
E866553
|
entity |
| Predicate | stateOfConflict |
P34508
|
FINISHED |
| Object | Louisiana in 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: Louisiana in the American Civil War | Statement: [Battle of Yellow Bayou, stateOfConflict, Louisiana in the American Civil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOfConflict Context triple: [Battle of Yellow Bayou, stateOfConflict, Louisiana in the American Civil War]
-
A.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
B.
regionOfConflict
chosen
Indicates that a specified region is the location where a particular conflict or dispute takes place.
-
C.
ongoingConflict
Indicates a sustained, unresolved state of opposition or hostilities continuing between the involved entities.
-
D.
allyInConflict
Indicates that one entity supports and cooperates with another entity as an ally within the context of a specific conflict or dispute.
-
E.
loreConflict
Indicates that there is an inconsistency, contradiction, or incompatibility between pieces of lore or canonical information.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: May 1, 2026, 1:46 a.m.