Triple

T9734841
Position Surface form Disambiguated ID Type / Status
Subject Norici E236031 entity
Predicate gaveNameTo P744 FINISHED
Object Noricum E46603 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: Noricum | Statement: [Norici, gaveNameTo, Noricum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Noricum
Context triple: [Norici, gaveNameTo, Noricum]
  • A. Noricum chosen
    Noricum was an ancient Celtic kingdom and later a Roman province located in the eastern Alps, roughly corresponding to modern Austria and parts of Slovenia.
  • B. Raetia
    Raetia was a frontier province of the Roman Empire in the central Alps region, covering parts of modern Switzerland, Germany, Austria, and Italy.
  • C. 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.
  • 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
    Moesia was an ancient Roman province located in the Balkans along the Danube River, encompassing parts of present-day Serbia and Bulgaria.
  • 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_69ca84d313e88190983ee6ffd0ef60d2 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9eebcec08190a9d4606fd26f2e19 completed April 1, 2026, 10:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1d5a1a3b88190a1b4561a9a780e41 completed April 5, 2026, 3:23 a.m.
Created at: March 30, 2026, 8:22 p.m.