Triple
T29204069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mortimer's Cross |
E740360
|
entity |
| Predicate | futureTitleOfCommander |
P39450
|
FINISHED |
| Object | Edward IV of England |
—
|
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 IV of England | Statement: [Battle of Mortimer's Cross, futureTitleOfCommander, Edward IV of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureTitleOfCommander Context triple: [Battle of Mortimer's Cross, futureTitleOfCommander, Edward IV of England]
-
A.
laterTitleOfCommander
chosen
Indicates that one title represents a later-held command position of the same commander who previously held another title.
-
B.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
C.
commanderTitle
Indicates the official rank or title held by the person who commands or leads a given entity.
-
D.
sideCommander
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
-
E.
frequentCommander
Indicates that one entity regularly serves as a commander or leader over another entity in repeated or numerous instances.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663c7b4f48190b66f966af570e768 |
completed | May 2, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:08 p.m.