Triple
T2815968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Selma (1865) |
E54286
|
entity |
| Predicate | UnionForcesType |
P43803
|
FINISHED |
| Object | cavalry |
—
|
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: cavalry | Statement: [Battle of Selma (1865), UnionForcesType, cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UnionForcesType Context triple: [Battle of Selma (1865), UnionForcesType, cavalry]
-
A.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
B.
formedByCoalition
Indicates that something (such as a group, government, or organization) came into existence through the alliance or joint effort of multiple distinct parties or factions.
-
C.
USForces
Indicates the presence, involvement, or deployment of United States military forces in relation to a specified location, event, or entity.
-
D.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
E.
alliedUnit
Indicates that one unit is associated as an ally or cooperative partner with another unit, typically sharing goals or working together.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde4ed4ac81909f1ec4a3f7869bc1 |
completed | March 7, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde0f4c648190b9812e64f30c39da |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 9:59 p.m.