Triple

T1901246
Position Surface form Disambiguated ID Type / Status
Subject Moesia E37692 entity
Predicate militaryRole P9463 FINISHED
Object Danubian limes E197883 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: Danubian limes | Statement: [Moesia, militaryRole, Danubian limes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Danubian limes
Context triple: [Moesia, militaryRole, Danubian limes]
  • A. Danube limes chosen
    The Danube limes was a major fortified frontier line of the Roman Empire along the Danube River, consisting of military camps, watchtowers, and fortifications that protected its northern border in Central and Eastern Europe.
  • B. Dacia Ripensis
    Dacia Ripensis was a late Roman province along the Danube frontier in the Balkans, known as a militarized border region of the empire.
  • C. Limonar
    Limonar is a municipality in western Cuba known for its agricultural activities and location within Matanzas Province.
  • D. Singidunum
    Singidunum was the ancient Roman and earlier Celtic settlement that occupied the site of present-day Belgrade, Serbia.
  • E. Arges
    Arges is one of the three primordial Cyclopes in Greek mythology, known as a one-eyed giant associated with thunder and lightning.
  • 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_69a8861be7148190a680937ec451a304 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb18da27c8190b315b462c857f4c2 completed March 7, 2026, 5:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69adeaf558148190b920693e2348190f completed March 8, 2026, 9:32 p.m.
Created at: March 4, 2026, 7:35 p.m.