Triple
T28715269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. claimed victory |
E729942
|
entity |
| Predicate | associatedWithOpposingForce |
—
|
GENERATED |
| Object | Seminole warriors |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithOpposingForce Context triple: [U.S. claimed victory, associatedWithOpposingForce, Seminole warriors]
-
A.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
-
B.
opposingUnits
chosen
Indicates that two units are in opposition to each other, such as being on rival sides, conflicting forces, or competing entities within a given context.
-
C.
hasOpposingForceType
Indicates that one force is characterized as being of a type that opposes or counteracts another force.
-
D.
opposingAlliance
Indicates that two entities belong to rival or mutually opposed alliances or factions.
-
E.
associatedWithWar
Indicates a relationship where an entity is connected or related to war, such as by involvement, influence, cause, or context.
- F. None of above.
Provenance (1 batch)
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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:50 a.m.