Triple
T19917809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Olustee |
E478709
|
entity |
| Predicate | objectiveOfUnion |
P129514
|
FINISHED |
| Object | restore Florida to the Union |
—
|
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: restore Florida to the Union | Statement: [Battle of Olustee, objectiveOfUnion, restore Florida to the Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveOfUnion Context triple: [Battle of Olustee, objectiveOfUnion, restore Florida to the Union]
-
A.
primaryUnionObjective
Indicates the main goal or purpose that a union seeks to achieve in its activities or negotiations.
-
B.
UnionObjective
Indicates that an entity has the goal, purpose, or objective of forming, maintaining, or advancing a union or unified organization.
-
C.
unionGoal
Indicates that the entities share a common objective or outcome they aim to achieve together as a unified group.
-
D.
aimOfUnionForces
chosen
Indicates the objective or strategic goal pursued by Union forces in a given context.
-
E.
endedUnionBetween
Indicates that one entity caused or marked the termination of a union, alliance, or partnership with 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_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.