Triple
T23160766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suessiones |
E578574
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Noviodunum |
—
|
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: Noviodunum | Statement: [Suessiones, capital, Noviodunum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Noviodunum Context triple: [Suessiones, capital, Noviodunum]
-
A.
Noviodunum
chosen
Noviodunum was an important Roman military and naval base on the lower Danube, in the province of Moesia (modern-day Romania).
-
B.
Ratae Corieltauvorum
Ratae Corieltauvorum was the Roman town and administrative center that later became the modern English city of Leicester.
-
C.
Teanum Sidicinum
Teanum Sidicinum was an important ancient city in Campania, Italy, serving as the chief urban center of the Sidicini people and later becoming a notable Roman municipality.
-
D.
Mamucium
Mamucium was a Roman fort and settlement that formed the early foundation of what is now the city of Manchester in northwest England.
-
E.
Aeclanum
Aeclanum was an ancient Samnite and later Roman town in southern Italy, notable as a strategic settlement along the Via Appia.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f006930819097aafef87405d737 |
completed | April 29, 2026, 4:54 a.m. |
Created at: April 17, 2026, 4:02 p.m.