Triple
T11570402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the River Raisin |
E274369
|
entity |
| Predicate | forcesInvolvedNative |
P57182
|
FINISHED |
| Object | Shawnee warriors |
—
|
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: Shawnee warriors | Statement: [Battle of the River Raisin, forcesInvolvedNative, Shawnee warriors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcesInvolvedNative Context triple: [Battle of the River Raisin, forcesInvolvedNative, Shawnee warriors]
-
A.
involvedForcesType
chosen
Indicates the type or category of forces that participate in or are associated with a given event, interaction, or situation.
-
B.
engagedForces
Indicates that one force has actively committed or deployed its military units against another force in combat or operational interaction.
-
C.
armedForcesInvolved
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
D.
specialForcesInvolved
Indicates that special forces units participate in or are involved in the referenced action, event, or operation.
-
E.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd543a48190b834abd8e8ae7b65 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.