Triple
T8383232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lake Okeechobee |
E197746
|
entity |
| Predicate | USForceStrength |
P81774
|
FINISHED |
| Object | approximately 1,000 soldiers |
—
|
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 1,000 soldiers | Statement: [Battle of Lake Okeechobee, USForceStrength, approximately 1,000 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USForceStrength Context triple: [Battle of Lake Okeechobee, USForceStrength, approximately 1,000 soldiers]
-
A.
USForceType
Indicates the type or category of U.S. military force involved in a given relationship or action.
-
B.
USForces
Indicates the presence, involvement, or deployment of United States military forces in relation to a specified location, event, or entity.
-
C.
stateOfForces
Indicates the condition, disposition, or readiness level of military or organizational forces at a given time.
-
D.
primaryUSForces
Indicates that the referenced forces constitute the main or principal contingent of United States military forces in a given context or operation.
-
E.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:02 p.m.