Triple

T19162506
Position Surface form Disambiguated ID Type / Status
Subject Suisse normande E469090 entity
Predicate hasTown P847 FINISHED
Object Thury-Harcourt-le-Hom NE NERFINISHED

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: Thury-Harcourt-le-Hom | Statement: [Suisse normande, hasTown, Thury-Harcourt-le-Hom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thury-Harcourt-le-Hom
Context triple: [Suisse normande, hasTown, Thury-Harcourt-le-Hom]
  • A. Thury-Harcourt-le-Hom chosen
    Thury-Harcourt-le-Hom is a commune in the Calvados department of northwestern France, known for its scenic location in the Suisse Normande region.
  • B. Seraincourt
    Seraincourt is a small commune in the Val-d'Oise department in the Île-de-France region of northern France.
  • C. Hampigny
    Hampigny is a small commune in the Aube department of north-central France.
  • D. Nancoury
    Nancoury is an alternative name for the Nancowry language, an Austroasiatic language spoken in India’s Nicobar Islands.
  • E. Héricourt
    Héricourt is a commune in eastern France known for its historical architecture and location within the Bourgogne-Franche-Comté region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dd084ff48190ac0f8c46ee722629 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5eebe03ac8190bbe0b34ebf0d90c6 completed April 20, 2026, 9:15 a.m.
Created at: April 10, 2026, 12:06 p.m.