Triple

T8227432
Position Surface form Disambiguated ID Type / Status
Subject Revolt of Vercingetorix E192206 entity
Predicate location P40 FINISHED
Object Alesia E560562 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: Alesia | Statement: [Revolt of Vercingetorix, location, Alesia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alesia
Context triple: [Revolt of Vercingetorix, location, Alesia]
  • A. Alesia chosen
    Alesia was an ancient fortified settlement in Gaul, best known as the site of Julius Caesar’s decisive victory over Vercingetorix in 52 BC.
  • 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. Singidunum
    Singidunum was the ancient Roman and earlier Celtic settlement that occupied the site of present-day Belgrade, Serbia.
  • D. Samarobriva
    Samarobriva is the ancient Roman name for the city now known as Amiens in northern France, which served as an important settlement in Roman Gaul.
  • E. Nikopol
    Nikopol is a historic city in central Ukraine located on the right bank of the Dnieper River, known for its industrial significance and role in regional trade and transport.
  • 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_69ca82db5b90819085d1ad7c2e27bfcc completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb77fdcb048190868ea4995b020a37 completed March 31, 2026, 7:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd34d4b6ec81909bc5d23bad1f326b completed April 1, 2026, 3:08 p.m.
Created at: March 30, 2026, 5:46 p.m.