Triple
T19251732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andematunnum |
E481407
|
entity |
| Predicate | connectedTo |
P37
|
FINISHED |
| Object | Durocortorum |
—
|
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: Durocortorum | Statement: [Andematunnum, connectedTo, Durocortorum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Durocortorum Context triple: [Andematunnum, connectedTo, Durocortorum]
-
A.
Durocortorum
chosen
Durocortorum was an important Roman city in northeastern Gaul, known today as Reims in France.
-
B.
Isurium Brigantum
Isurium Brigantum was a significant Roman town and military center in northern Britain, located at modern Aldborough in North Yorkshire.
-
C.
Duranus
Duranus is a small rural commune in southeastern France, located in the Alpes-Maritimes department in the Provence-Alpes-Côte d’Azur region.
-
D.
Noviodunum
Noviodunum was an important Roman military and naval base on the lower Danube, in the province of Moesia (modern-day Romania).
-
E.
Luguvalium
Luguvalium was a significant Roman settlement and military center in northern Britain, located at the site of modern-day Carlisle.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb30bf6c819094c44aceb544a023 |
completed | April 20, 2026, 10:08 a.m. |
Created at: April 10, 2026, 1:28 p.m.