Triple
T8383233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lake Okeechobee |
E197746
|
entity |
| Predicate | SeminoleForceStrength |
P1404
|
FINISHED |
| Object | approximately 380 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: approximately 380 warriors | Statement: [Battle of Lake Okeechobee, SeminoleForceStrength, approximately 380 warriors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SeminoleForceStrength Context triple: [Battle of Lake Okeechobee, SeminoleForceStrength, approximately 380 warriors]
-
A.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
B.
commandingForce1Strength
Indicates that one entity has a certain level or measure of strength in its role as the primary commanding force over another entity or situation.
-
C.
combatantStrength
chosen
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
D.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
E.
USForceType
Indicates the type or category of U.S. military force involved in a given relationship or action.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80ddc0f08190a90d4d9070bf713b |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:02 p.m.