Triple
T1375271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Edgehill |
E29206
|
entity |
| Predicate | RoyalistSide |
P27100
|
FINISHED |
| Object | supporters 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: supporters of King Charles I | Statement: [Battle of Edgehill, RoyalistSide, supporters of King Charles I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RoyalistSide Context triple: [Battle of Edgehill, RoyalistSide, supporters of King Charles I]
-
A.
RoyalistForceStrength
Indicates the size or level of military power possessed by a royalist-aligned force in a given context.
-
B.
RoyalistArmyOutcome
Indicates the result or consequence experienced by the Royalist army in a particular conflict or event.
-
C.
royalistObjective
Indicates that an entity’s goal, purpose, or intended outcome is to support, preserve, or advance a monarchy or royal authority.
-
D.
opponentInWarOfTheSpanishSuccession
Indicates that two entities were opposing sides against each other in the War of the Spanish Succession.
-
E.
allyInWarOfTheSpanishSuccession
Indicates that the subject entity was an ally of the object entity during the War of the Spanish Succession.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c2f7aeb08190b52ef1058c18327e |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befcabdc8190a9f05d002603f81c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0335f7081908d50046ced4cdee0 |
completed | March 1, 2026, 10:39 p.m. |
Created at: March 1, 2026, 7:59 p.m.