Triple
T863078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Naseby |
E18639
|
entity |
| Predicate | RoyalistArmy |
P4889
|
FINISHED |
| Object | main field army of King Charles I |
—
|
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: main field army of King Charles I | Statement: [Battle of Naseby, RoyalistArmy, main field army of King Charles I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RoyalistArmy Context triple: [Battle of Naseby, RoyalistArmy, main field army of King Charles I]
-
A.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
B.
militaryOrganization
chosen
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
C.
notableCommanderSide
Indicates that a particular military or strategic side is notably commanded or led by a specified commander.
-
D.
commandingOfficerBritishSide
Indicates that one entity serves as the commanding officer of another entity on the British side in a military context.
-
E.
occupationForcesCommandedBy
Indicates that a particular occupation force is under the command or authority of a specified commander or commanding 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac67d4d481909487d3edb3e46936 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa86065881909d477e26fdd84d45 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.