Triple
T19917811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Olustee |
E478709
|
entity |
| Predicate | objectiveOfConfederacy |
P25419
|
FINISHED |
| Object | defend Florida |
—
|
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: defend Florida | Statement: [Battle of Olustee, objectiveOfConfederacy, defend Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveOfConfederacy Context triple: [Battle of Olustee, objectiveOfConfederacy, defend Florida]
-
A.
primaryObjectiveConfederate
Indicates that the confederate’s main goal, purpose, or target within a given context is the specified objective.
-
B.
ConfederateObjective
chosen
Indicates that an action or plan is aimed at achieving a goal or objective of the Confederate side in a conflict or war.
-
C.
objectiveOfRepublicanForces
Indicates that a specified goal, target, or aim is pursued or held by Republican forces.
-
D.
objectiveOfUSForces
Indicates that a specified goal, target, or mission serves as an objective assigned to or pursued by U.S. military forces.
-
E.
UnionObjective
Indicates that an entity has the goal, purpose, or objective of forming, maintaining, or advancing a union or unified organization.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65995bd60819097cfad003dd29731 |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.