Triple
T28174419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atrebates |
E715549
|
entity |
| Predicate | provinceAfterConquest |
P73521
|
FINISHED |
| Object | Britannia |
—
|
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: Britannia | Statement: [Atrebates, provinceAfterConquest, Britannia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceAfterConquest Context triple: [Atrebates, provinceAfterConquest, Britannia]
-
A.
realmConqueredBy
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
-
B.
afterConquestBy
Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
-
C.
convertedAfterConquest
Indicates that one entity underwent conversion (typically religious or cultural) as a direct consequence of being conquered by another entity.
-
D.
romanProvinceAfterConquest
chosen
Indicates that a territory became a Roman province following its military conquest by Rome.
-
E.
afterConquestName
Indicates that an entity’s name is the one it is known by after a conquest or successful takeover has occurred.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 27, 2026, 10:15 p.m.