Triple
T13570751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxon Shore forts |
E324152
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Regulbium |
E806165
|
NE 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: Regulbium | Statement: [Saxon Shore forts, hasPart, Regulbium]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Regulbium Context triple: [Saxon Shore forts, hasPart, Regulbium]
-
A.
Regulbium
chosen
Regulbium was the Roman-era coastal fort and settlement that later became known as Reculver in Kent, England.
-
B.
Albium Ingaunum
Albium Ingaunum was an important ancient Ligurian coastal city, located in what is now Albenga on the Italian Riviera.
-
C.
Ormenium
Ormenium was an ancient town in the region of Magnesia in Thessaly, Greece, known from classical sources such as Homer’s Iliad.
-
D.
Luisium
Luisium is a historic neoclassical palace with surrounding landscaped grounds that forms part of the UNESCO-listed Garden Kingdom of Dessau-Wörlitz in Germany.
-
E.
Agyrium
Agyrium was an ancient city in central Sicily, historically significant as the birthplace of the Greek historian Diodorus Siculus.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00f5b8881908617f42d227ed137 |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bb61a40819099a62f65a68dff7b |
completed | May 3, 2026, 3:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.