Triple

T12923318
Position Surface form Disambiguated ID Type / Status
Subject Burridge E309177 entity
Predicate hasVariantSpelling P457 FINISHED
Object Burrige E309177 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: Burrige | Statement: [Burridge, hasVariantSpelling, Burrige]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burrige
Context triple: [Burridge, hasVariantSpelling, Burrige]
  • A. Burridge chosen
    Burridge is an English surname of likely locational origin, associated with various places and families in the United Kingdom.
  • B. Buron
    Buron is a small village in northwestern France, historically notable for fighting during the Battle of Normandy in World War II.
  • C. Barkur
    Barkur is a historic town in the Udupi district of Karnataka, India, known for its ancient temples, archaeological sites, and cultural heritage.
  • D. Bekwarra
    Bekwarra is a notable town and local government area in southeastern Nigeria, recognized for its predominantly agrarian community and cultural heritage within Cross River State.
  • E. Burglauer
    Burglauer is a small municipality in the Rhön-Grabfeld district of northern Bavaria, Germany.
  • 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_69d7bdfa933c8190b5a27aa4a08a19b7 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d971e9576c81908eb59569af6da877 completed April 10, 2026, 9:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6b8d39d4c81908fab65129f292862 completed May 3, 2026, 2:54 a.m.
Created at: April 9, 2026, 5:42 p.m.