Triple
T13447280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Étang de Berre |
E320515
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Fos-sur-Mer |
E457578
|
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: Fos-sur-Mer | Statement: [Étang de Berre, locatedNear, Fos-sur-Mer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fos-sur-Mer Context triple: [Étang de Berre, locatedNear, Fos-sur-Mer]
-
A.
Fos-sur-Mer
chosen
Fos-sur-Mer is a coastal industrial town in southern France known for its large port facilities and heavy industry along the Mediterranean.
-
B.
Bény-sur-Mer
Bény-sur-Mer is a small commune in the Calvados department of Normandy in northwestern France, near the historic D-Day landing beaches.
-
C.
Dives-sur-Mer
Dives-sur-Mer is a coastal commune in northwestern France, known for its historic harbor linked to William the Conqueror’s 1066 expedition to England.
-
D.
Luc-sur-Mer
Luc-sur-Mer is a coastal commune in northwestern France, situated on the English Channel in the Normandy region.
-
E.
Saint-Laurent-sur-Mer
Saint-Laurent-sur-Mer is a coastal commune in Normandy, France, historically significant for its location at the heart of the D-Day landings during World War II.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaef758b08190b9aa5ec7082cd417 |
completed | April 12, 2026, 2:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c0d591648190beb4430c6b199eb8 |
completed | May 3, 2026, 9:40 p.m. |
Created at: April 9, 2026, 9:41 p.m.