Triple

T9587569
Position Surface form Disambiguated ID Type / Status
Subject Roman city walls of Verulamium E231329 entity
Predicate locatedIn P40 FINISHED
Object Verulamium E191343 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: Verulamium | Statement: [Roman city walls of Verulamium, locatedIn, Verulamium]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Verulamium
Context triple: [Roman city walls of Verulamium, locatedIn, Verulamium]
  • A. Verulamium chosen
    Verulamium was a major Roman town in Britain, located near modern St Albans, known for its archaeological remains including mosaics, a theatre, and city walls.
  • B. Camulodunum
    Camulodunum was an important ancient Roman town in Britain, serving as the first provincial capital and a major military and administrative center.
  • C. Dacorum
    Dacorum is a local government district and borough in Hertfordshire, England, encompassing towns such as Hemel Hempstead and Berkhamsted.
  • D. Londinium
    Londinium was the major Roman city and commercial hub that later evolved into modern-day London.
  • E. Eboracum
    Eboracum was the major Roman fortress and city that later became the English city of York, serving as an important military and administrative center in Roman Britain.
  • 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_69ca848161688190a68d514a0a9d5129 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd99f01ca08190afaa44645a58e918 completed April 1, 2026, 10:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69d190dd38e48190aef80bb7a153bff6 completed April 4, 2026, 10:29 p.m.
Created at: March 30, 2026, 8:06 p.m.