Triple
T29204083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mortimer's Cross |
E740360
|
entity |
| Predicate | executedAfterBattle |
P98629
|
FINISHED |
| Object | Owen Tudor |
—
|
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: Owen Tudor | Statement: [Battle of Mortimer's Cross, executedAfterBattle, Owen Tudor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executedAfterBattle Context triple: [Battle of Mortimer's Cross, executedAfterBattle, Owen Tudor]
-
A.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
B.
postBattleEvent
chosen
Indicates an event or occurrence that takes place after a battle has concluded.
-
C.
missionPhaseAfter
Indicates that one mission phase occurs later in sequence or time than another mission phase.
-
D.
functionDuringBattle
Indicates a functional role, effect, or behavior that specifically occurs or is active during a battle.
-
E.
operatorAfterWar
Indicates that one entity serves or functions as an operator after the occurrence or end of a war.
- 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_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:08 p.m.