Triple

T16762127
Position Surface form Disambiguated ID Type / Status
Subject Ouistreham lock E407371 entity
Predicate municipality P852 FINISHED
Object Ouistreham E90830 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: Ouistreham | Statement: [Ouistreham lock, municipality, Ouistreham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ouistreham
Context triple: [Ouistreham lock, municipality, Ouistreham]
  • A. Ouistreham chosen
    Ouistreham is a coastal town in Normandy, France, known for its ferry port and its location at the eastern end of the D-Day landing area of Sword Beach.
  • B. Secqueville-en-Bessin
    Secqueville-en-Bessin is a small commune in the Calvados department of the Normandy region in northwestern France.
  • C. Wimereux
    Wimereux is a seaside resort town on France’s northern Opal Coast, known for its sandy beaches, Belle Époque villas, and coastal promenades.
  • D. Heuqueville
    Heuqueville is a small French commune located in the Normandy region, forming part of the greater Le Havre metropolitan area.
  • E. Port-en-Bessin-Huppain
    Port-en-Bessin-Huppain is a coastal commune in Normandy, France, known for its fishing harbor and its location near the historic D-Day landing beaches.
  • 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_69d8839174188190909f190097207065 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3abed67f88190afb1d392ff01a5e7 completed April 18, 2026, 4:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00b283a9808190ba76110cf3c7f3a9 completed May 10, 2026, 4:29 p.m.
Created at: April 10, 2026, 5:21 a.m.