Triple

T9642001
Position Surface form Disambiguated ID Type / Status
Subject Bovingdon E233094 entity
Predicate locatedIn P40 FINISHED
Object Dacorum E361400 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: Dacorum | Statement: [Bovingdon, locatedIn, Dacorum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dacorum
Context triple: [Bovingdon, locatedIn, Dacorum]
  • A. Dacorum chosen
    Dacorum is a local government district and borough in Hertfordshire, England, encompassing towns such as Hemel Hempstead and Berkhamsted.
  • B. Verulamium
    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.
  • C. Londinium
    Londinium was the major Roman city and commercial hub that later evolved into modern-day London.
  • D. Ratae Corieltauvorum
    Ratae Corieltauvorum was the Roman town and administrative center that later became the modern English city of Leicester.
  • E. Lugdunum
    Lugdunum was the principal Roman city in Gaul, serving as a major administrative, commercial, and cultural center of the Roman Empire in what is now Lyon, France.
  • 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_69ca848a5a908190aad251f4137b0c3a completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9b566a2881909ab3f9502b1c3c8d completed April 1, 2026, 10:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69d19f6a7ddc8190b7e8add97b7dc257 completed April 4, 2026, 11:31 p.m.
Created at: March 30, 2026, 8:12 p.m.