Triple
T18938603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viroconium Cornoviorum |
E463319
|
entity |
| Predicate | postRomanReuse |
P133875
|
FINISHED |
| Object | stone robbed for local buildings |
—
|
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: stone robbed for local buildings | Statement: [Viroconium Cornoviorum, postRomanReuse, stone robbed for local buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postRomanReuse Context triple: [Viroconium Cornoviorum, postRomanReuse, stone robbed for local buildings]
-
A.
usedInRomanPeriodFor
Indicates that something served a particular function, purpose, or application during the Roman period.
-
B.
postRomanSuccessor
Indicates that one entity serves as the political or cultural successor to another entity following the end of Roman rule.
-
C.
hasRomanRemains
Indicates that the subject contains or is the location of physical remains or archaeological evidence from the Roman period.
-
D.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
E.
preRomanStatus
Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
- F. None of above. chosen
Provenance (4 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3ea39dc8190a2f773e09e11e6d1 |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.