Triple

T1166735
Position Surface form Disambiguated ID Type / Status
Subject Gaul E24814 entity
Predicate majorCity P316 FINISHED
Object Lugdunum E78794 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: Lugdunum | Statement: [Gaul, majorCity, Lugdunum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lugdunum
Context triple: [Gaul, majorCity, Lugdunum]
  • A. Lugdunum chosen
    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.
  • B. Lugdunum Convenarum
    Lugdunum Convenarum was an ancient Roman town in southwestern Gaul (near modern Saint-Bertrand-de-Comminges, France), known as a regional center in the foothills of the Pyrenees.
  • C. Argentoratum
    Argentoratum is the ancient Roman military camp and settlement that later developed into the modern city of Strasbourg in northeastern France.
  • D. Augusta Treverorum
    Augusta Treverorum was the Roman city that became a major imperial residence and administrative center in the late Roman Empire, located at the site of modern-day Trier in Germany.
  • E. Aquincum
    Aquincum was an important ancient Roman military and civilian settlement located in what is now northern Budapest, Hungary.
  • 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_69a494082a7c819095004f423f294a64 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bccd75048190b8ce88237c1a748b completed March 1, 2026, 10:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac6f17aa608190920b7df62b8dd903 completed March 7, 2026, 6:31 p.m.
Created at: March 1, 2026, 7:45 p.m.