Triple
T29204088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mortimer's Cross |
E740360
|
entity |
| Predicate | primaryYorkistLeader |
P202852
|
FINISHED |
| Object | Edward, Earl of March |
—
|
NE NERFINISHED |
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: Edward, Earl of March | Statement: [Battle of Mortimer's Cross, primaryYorkistLeader, Edward, Earl of March]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryYorkistLeader Context triple: [Battle of Mortimer's Cross, primaryYorkistLeader, Edward, Earl of March]
-
A.
primaryRoyalistCavalryLeader
Indicates that someone serves as the main commanding leader of cavalry forces aligned with the Royalist side.
-
B.
LancastrianCommander
Indicates that the subject serves as a military commander aligned with the Lancastrian side in the Wars of the Roses.
-
C.
CharlesTheBoldRole
Indicates the role, position, or capacity in which Charles the Bold is acting or is characterized in a given context.
-
D.
aimOfYorkists
Indicates that the referenced goal, objective, or purpose is one pursued or intended by the Yorkist faction.
-
E.
royalistLeader
Indicates that one entity is the leader of a royalist faction, movement, or cause in relation to another entity.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a00c59b03dc8190870f0dd24603a1ef |
completed | May 10, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a00c5178bc88190b2a0e03f38314035 |
completed | May 10, 2026, 5:49 p.m. |
| PDg | Predicate description generation | batch_6a00c59a1af88190848c5b1775af9caa |
completed | May 10, 2026, 5:51 p.m. |
Created at: April 28, 2026, 12:08 p.m.