Triple

T2923759
Position Surface form Disambiguated ID Type / Status
Subject Lugdunum E78794 entity
Predicate latinName P3646 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: [Lugdunum, latinName, Lugdunum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lugdunum
Context triple: [Lugdunum, latinName, 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. Londinium
    Londinium was the major Roman city and commercial hub that later evolved into modern-day London.
  • C. Ratae Corieltauvorum
    Ratae Corieltauvorum was the Roman town and administrative center that later became the modern English city of Leicester.
  • D. 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.
  • 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_69ad8b0d40b481908bc2a5fa2e73c3fb completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad97bf2df88190bd4f1e90d4656507 completed March 8, 2026, 3:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69b056375b5c819081c7d4fd506cbf25 completed March 10, 2026, 5:34 p.m.
Created at: March 8, 2026, 2:55 p.m.