Triple

T14137525
Position Surface form Disambiguated ID Type / Status
Subject Battle of Tinchebray E350336 entity
Predicate hasLocation P40 FINISHED
Object Tinchebray E532250 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: Tinchebray | Statement: [Battle of Tinchebray, hasLocation, Tinchebray]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tinchebray
Context triple: [Battle of Tinchebray, hasLocation, Tinchebray]
  • A. Tinchebray chosen
    Tinchebray is a small commune in northwestern France, historically part of Normandy and known as the birthplace of Surrealist writer André Breton.
  • B. Aymestrey
    Aymestrey is a small village in Herefordshire, England, known for its rural setting near the River Lugg and its historic church and timber-framed buildings.
  • C. Seraincourt
    Seraincourt is a small commune in the Val-d'Oise department in the Île-de-France region of northern France.
  • D. Hawkenbury
    Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
  • E. Kintbury
    Kintbury is a rural village in Berkshire, England, known for its picturesque countryside setting and historic charm.
  • 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_69d827865f608190b311820428ae027b completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de610fb86c81909eb26bf9c13696ca completed April 14, 2026, 3:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcdf16079c819080a74cd8a6eb37a6 completed May 7, 2026, 6:51 p.m.
Created at: April 10, 2026, 12:33 a.m.