Triple
T16453088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Côte de Nacre |
E399602
|
entity |
| Predicate | hasTown |
P847
|
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: [Côte de Nacre, hasTown, Ouistreham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ouistreham Context triple: [Côte de Nacre, hasTown, 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ce259d88190803930051409d72c |
completed | April 18, 2026, 7:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00607618c8819090fc9f18ae5f30dd |
completed | May 10, 2026, 10:39 a.m. |
Created at: April 10, 2026, 5:10 a.m.