Triple
T26304618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Myton |
E661646
|
entity |
| Predicate | EnglishForcesType |
P87941
|
FINISHED |
| Object | militia |
—
|
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: militia | Statement: [Battle of Myton, EnglishForcesType, militia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EnglishForcesType Context triple: [Battle of Myton, EnglishForcesType, militia]
-
A.
englishForcesType
chosen
Indicates the type or category of English military forces involved in a given context or action.
-
B.
BritishForcesType
Indicates that an entity is classified as a type or category within the British armed forces.
-
C.
enemyForceType
Indicates that one entity is characterized as a hostile or opposing force of a specified type relative to another entity.
-
D.
EnglishFleetEffect
Indicates the impact or influence exerted by the English fleet on another entity, situation, or outcome.
-
E.
forzaBelligerante
Indicates a party’s status or role as a belligerent force engaged in a conflict or 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee22a908190a62640e48c2e7659 |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:18 p.m.