Triple

T17655656
Position Surface form Disambiguated ID Type / Status
Subject Legio VIII Augusta E429614 entity
Predicate garrison P75 FINISHED
Object Argentoratum 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: Argentoratum | Statement: [Legio VIII Augusta, garrison, Argentoratum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Argentoratum
Context triple: [Legio VIII Augusta, garrison, Argentoratum]
  • A. Argentoratum chosen
    Argentoratum is the ancient Roman military camp and settlement that later developed into the modern city of Strasbourg in northeastern France.
  • B. Mogontiacum
    Mogontiacum was the major Roman military and administrative settlement that later developed into the modern German city of Mainz.
  • C. Aquincum
    Aquincum was an important ancient Roman military and civilian settlement located in what is now northern Budapest, Hungary.
  • D. 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.
  • E. Luguvalium
    Luguvalium was a significant Roman settlement and military center in northern Britain, located at the site of modern-day Carlisle.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889e2c2608190b762e76d9b2262f1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46e40e344819086a49c69f8f2956b completed April 19, 2026, 5:55 a.m.
Created at: April 10, 2026, 6:06 a.m.