Triple
T17010569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Britannia |
E412686
|
entity |
| Predicate | endOfExistenceEvent |
P48547
|
FINISHED |
| Object | withdrawal of Roman rule from Britain |
—
|
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: withdrawal of Roman rule from Britain | Statement: [Britannia, endOfExistenceEvent, withdrawal of Roman rule from Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfExistenceEvent Context triple: [Britannia, endOfExistenceEvent, withdrawal of Roman rule from Britain]
-
A.
eschatologicalEvent
Indicates an event associated with ultimate destiny or final outcomes in a religious or philosophical end-times framework.
-
B.
extinctionEvent
Indicates a large-scale occurrence that causes the widespread or complete disappearance of one or more species or higher taxonomic groups.
-
C.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
D.
endOf
chosen
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
E.
extinctionPeriod
Indicates the time span during which an entity ceases to exist or is considered extinct.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d47bcb508190a799f0bad6b70245 |
completed | April 18, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.