Triple
T28359260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verlamion |
E718317
|
entity |
| Predicate | preRomanNameOf |
P51753
|
FINISHED |
| Object | Verulamium area |
—
|
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: Verulamium area | Statement: [Verlamion, preRomanNameOf, Verulamium area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preRomanNameOf Context triple: [Verlamion, preRomanNameOf, Verulamium area]
-
A.
preRomanName
chosen
Indicates the name by which an entity (such as a place or people) was known before the Roman period or prior to receiving a Roman-era name.
-
B.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
C.
preRomanLanguage
Indicates that a language existed or was used in a region before the arrival or dominance of Roman rule or the Latin language.
-
D.
fullRomanName
Indicates that one entity is the complete Roman-style personal name (including all components) corresponding to another entity.
-
E.
hasRomanName
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c3048248190b55266211394ecb7 |
completed | May 2, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:51 a.m.