Triple

T5968228
Position Surface form Disambiguated ID Type / Status
Subject Sousse E132805 entity
Predicate historicalName P65 FINISHED
Object Hadrumetum (Byzantine city) E216963 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: Hadrumetum (Byzantine city) | Statement: [Sousse, historicalName, Hadrumetum (Byzantine city)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hadrumetum (Byzantine city)
Context triple: [Sousse, historicalName, Hadrumetum (Byzantine city)]
  • A. Thysdrus
    Thysdrus was an important Roman-era city in present-day El Jem, Tunisia, known for its prosperity and monumental amphitheatre.
  • B. Durostorum
    Durostorum was a major Roman military and urban center on the lower Danube, located in the province of Moesia (modern Silistra, Bulgaria).
  • C. Hadrianopolis
    Hadrianopolis was an important ancient Roman and Byzantine city in Thrace, later known as Edirne in modern-day Turkey.
  • D. Hadrumetum chosen
    Hadrumetum was an important ancient Phoenician and later Roman port city located on the coast of modern-day Tunisia.
  • E. Neocaesarea in Pontus
    Neocaesarea in Pontus was an important city in the Roman province of Pontus in Asia Minor, known as a regional center of early Christianity.
  • 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_69c0086deab081908550159ca23eec9b completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c03a3f612481908744cb645f2ede1d completed March 22, 2026, 6:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0e40506848190843971e772d56054 completed March 23, 2026, 6:56 a.m.
Created at: March 22, 2026, 4:03 p.m.