Triple

T17163749
Position Surface form Disambiguated ID Type / Status
Subject Bénouville Bridge E416551 entity
Predicate locatedIn P40 FINISHED
Object Bénouville E407369 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: Bénouville | Statement: [Bénouville Bridge, locatedIn, Bénouville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bénouville
Context triple: [Bénouville Bridge, locatedIn, Bénouville]
  • A. Bénouville chosen
    Bénouville is a commune in the Calvados department of Normandy in northwestern France, known for its historic Pegasus Bridge from World War II.
  • B. Bouville
    Bouville is the fictional French seaside town that serves as the primary setting of Jean-Paul Sartre’s existentialist novel "Nausea."
  • C. Frémainville
    Frémainville is a small commune in the Val-d'Oise department in the Île-de-France region of northern France.
  • D. Isneauville
    Isneauville is a small commune in northern France, situated in the Normandy region near the city of Rouen.
  • E. Val-de-Reuil
    Val-de-Reuil is a planned new town and commune in northern France, located in the Eure department of the Normandy region.
  • 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_69d886d279c081909f8ff1f743ddeb69 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3f913c84481908bb5da8bcc6a2e62 completed April 18, 2026, 9:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a01483969a48190a90268c9560b8cd7 completed May 11, 2026, 3:08 a.m.
Created at: April 10, 2026, 5:37 a.m.