Triple

T12987403
Position Surface form Disambiguated ID Type / Status
Subject Lovech E321804 entity
Predicate partOfHistoricalRegion P13711 FINISHED
Object Moesia E37692 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: Moesia | Statement: [Lovech, partOfHistoricalRegion, Moesia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moesia
Context triple: [Lovech, partOfHistoricalRegion, Moesia]
  • A. Moesia chosen
    Moesia was an ancient Roman province located in the Balkans along the Danube River, encompassing parts of present-day Serbia and Bulgaria.
  • B. Moesia Secunda
    Moesia Secunda was a late Roman province in the Balkans, formed from the reorganization of earlier Moesian territories and strategically located along the lower Danube frontier.
  • C. Moesia Superior
    Moesia Superior was a Roman imperial province located in the central Balkans along the Danube, encompassing parts of modern-day Serbia and surrounding regions.
  • D. Moesia Inferior
    Moesia Inferior was a Roman province located in the lower Danube region, roughly corresponding to parts of modern-day Bulgaria and Romania.
  • E. Moesia Prima
    Moesia Prima was a late Roman province located in the central Balkans along the Danube frontier, in what is now mainly eastern Serbia.
  • 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_69d8076479b8819090afce3591939cdf completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97e5f47ec8190b39107bc016f9824 completed April 10, 2026, 10:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6cbc277c881909ae77e8a44e06986 completed May 3, 2026, 4:14 a.m.
Created at: April 9, 2026, 8:41 p.m.