Triple
T13313009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pays de Caux |
E317118
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Fécamp |
E366745
|
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: Fécamp | Statement: [Pays de Caux, contains, Fécamp]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fécamp Context triple: [Pays de Caux, contains, Fécamp]
-
A.
Fécamp
chosen
Fécamp is a coastal town and former important fishing port in northern France, known for its historic Benedictine Palace and dramatic cliffs along the English Channel.
-
B.
Colleville-sur-Mer
Colleville-sur-Mer is a commune in Normandy, France, best known for its location by the D-Day landing beaches and the Normandy American Cemetery.
-
C.
Isigny-sur-Mer
Isigny-sur-Mer is a coastal commune in Normandy, France, renowned for its dairy products—especially butter and cream—and its historic port.
-
D.
Harfleur
Harfleur is a historic port town in Normandy, northern France, known for its strategic importance during the Hundred Years’ War.
-
E.
Boulogne-sur-Mer
Boulogne-sur-Mer is a coastal city and major fishing port in northern France, located on the English Channel in the Pas-de-Calais department.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d990f6d34c8190ba19dc2df7d42c22 |
completed | April 11, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f73061e90c81909badb0cd12b304a2 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 9:29 p.m.