Triple
T33777396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venta Icenorum |
E865557
|
entity |
| Predicate | postRomanSuccessorSettlement |
P84570
|
FINISHED |
| Object | Caistor St Edmund |
—
|
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: Caistor St Edmund | Statement: [Venta Icenorum, postRomanSuccessorSettlement, Caistor St Edmund]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postRomanSuccessorSettlement Context triple: [Venta Icenorum, postRomanSuccessorSettlement, Caistor St Edmund]
-
A.
postRomanSuccessor
chosen
Indicates that one entity serves as the political or cultural successor to another entity following the end of Roman rule.
-
B.
becameRomanColony
Indicates that a place or community transitioned into the formal status of a Roman colony under Roman authority.
-
C.
statusAfterRomanConquest
Indicates the condition or standing of an entity following its conquest by the Roman state or Roman forces.
-
D.
romanProvinceAfterConquest
Indicates that a territory became a Roman province following its military conquest by Rome.
-
E.
preRomanPolity
Indicates that an entity functioned as a political or governmental unit that existed before the establishment or dominance of Roman rule in a given region.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.