Triple

T16451922
Position Surface form Disambiguated ID Type / Status
Subject Regio IV Samnium E399571 entity
Predicate contains P35 FINISHED
Object Teanum Sidicinum E227805 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: Teanum Sidicinum | Statement: [Regio IV Samnium, contains, Teanum Sidicinum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Teanum Sidicinum
Context triple: [Regio IV Samnium, contains, Teanum Sidicinum]
  • A. Teanum Sidicinum chosen
    Teanum Sidicinum was an important ancient city in Campania, Italy, serving as the chief urban center of the Sidicini people and later becoming a notable Roman municipality.
  • B. Atuatuca Tungrorum
    Atuatuca Tungrorum was an important Roman-era city and military center in the province of Gallia Belgica, located at the site of modern-day Tongeren in Belgium.
  • C. Ratae Corieltauvorum
    Ratae Corieltauvorum was the Roman town and administrative center that later became the modern English city of Leicester.
  • D. Mogontiacum
    Mogontiacum was the major Roman military and administrative settlement that later developed into the modern German city of Mainz.
  • E. Hadrumetum
    Hadrumetum was an important ancient Phoenician and later Roman port city located on the coast of modern-day Tunisia.
  • 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_69d87f2c6778819080fcfae53be8f12a completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32ce19344819083d323077b742bc3 completed April 18, 2026, 7:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004f4e31a08190b121d0cfe2a406c2 completed May 10, 2026, 9:26 a.m.
Created at: April 10, 2026, 5:10 a.m.