Triple
T8737454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corinium Dobunnorum |
E207420
|
entity |
| Predicate | rankInRomanBritain |
P50574
|
FINISHED |
| Object | one of the largest towns |
—
|
LITERAL 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: one of the largest towns | Statement: [Corinium Dobunnorum, rankInRomanBritain, one of the largest towns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInRomanBritain Context triple: [Corinium Dobunnorum, rankInRomanBritain, one of the largest towns]
-
A.
wasRomanFort
Indicates that the subject functioned as a Roman military fort at some point in time.
-
B.
rankInRomanEast
Indicates that one entity holds a specific rank or position within the administrative, military, or social hierarchy of the Roman East relative to another entity or context.
-
C.
wasRomanTown
chosen
Indicates that the subject entity functioned as a town or urban settlement during the period of the Roman Empire.
-
D.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
E.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d45c96081909aa8509064ff3a04 |
completed | March 31, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69cc457322b481908712a9630a17b954 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:38 p.m.