Triple

T12630041
Position Surface form Disambiguated ID Type / Status
Subject historical province of Burgundy E301615 entity
Predicate contains P35 FINISHED
Object Autun E162613 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: Autun | Statement: [historical province of Burgundy, contains, Autun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Autun
Context triple: [historical province of Burgundy, contains, Autun]
  • A. Autun chosen
    Autun is a historic town in eastern France renowned for its well-preserved Roman ruins and medieval cathedral.
  • B. Arrah
    Arrah is a historic town in the Indian state of Bihar, known for its role as a key site of conflict during the Indian Rebellion of 1857.
  • C. Larimore
    Larimore is a small city in eastern North Dakota, United States, known for its rural character and proximity to Grand Forks.
  • D. Holladay
    Holladay is a suburban city in the Salt Lake City metropolitan area in northern Utah, known for its residential neighborhoods and proximity to the Wasatch Mountains.
  • E. Scobey
    Scobey is a surname and place name most notably associated with the city of Scobey in Montana, United States.
  • 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_69d7bdeaf49c8190b13800111fa77ea3 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9610ce9e48190a496824002c0d2be completed April 10, 2026, 8:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69f65edafc7c819088bd641542a32e39 completed May 2, 2026, 8:30 p.m.
Created at: April 9, 2026, 5:15 p.m.