Triple
T29015807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allectus |
E737302
|
entity |
| Predicate | defeatResult |
P119273
|
FINISHED |
| Object | reunification of Britain with Roman Empire |
—
|
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: reunification of Britain with Roman Empire | Statement: [Allectus, defeatResult, reunification of Britain with Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defeatResult Context triple: [Allectus, defeatResult, reunification of Britain with Roman Empire]
-
A.
defeat
Indicates that one entity wins against and overcomes another in a contest, conflict, or competition.
-
B.
defeatEffect
chosen
Indicates that one entity’s defeat causes a particular outcome or change to occur for another entity or the overall situation.
-
C.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
D.
defeatedDespite
Indicates that one entity successfully defeated another entity even though circumstances or expectations suggested that defeat would be unlikely or difficult.
-
E.
sideDefeated
Indicates that one side in a conflict, competition, or contest has been beaten or overcome by another side.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fe0772881909b1fbc2e28a1206a |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:45 a.m.