Triple
T22452962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigantes |
E555038
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Isurium Brigantum |
—
|
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: Isurium Brigantum | Statement: [Brigantes, capital, Isurium Brigantum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Isurium Brigantum Context triple: [Brigantes, capital, Isurium Brigantum]
-
A.
Isurium Brigantum
chosen
Isurium Brigantum was a significant Roman town and military center in northern Britain, located at modern Aldborough in North Yorkshire.
-
B.
Brigantium
Brigantium was a significant Roman-era settlement in the province of Raetia, located near present-day Bregenz on the eastern shore of Lake Constance.
-
C.
Noviodunum
Noviodunum was an important Roman military and naval base on the lower Danube, in the province of Moesia (modern-day Romania).
-
D.
Durocortorum
Durocortorum was an important Roman city in northeastern Gaul, known today as Reims in France.
-
E.
Durnovaria
Durnovaria was the Roman-era town that occupied the site of modern Dorchester in Dorset, England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4d6368819082cafbbd83339fbf |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 16, 2026, 8:48 p.m.