Triple
T26239077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernières-sur-Mer |
E656257
|
entity |
| Predicate | coastalCommune |
P160539
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Bernières-sur-Mer, coastalCommune, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalCommune Context triple: [Bernières-sur-Mer, coastalCommune, true]
-
A.
hasCoastalCommunes
Indicates that an administrative region possesses one or more communes that are located on or directly adjacent to a sea or ocean coastline.
-
B.
hasCommune
Indicates a relationship where an entity is associated with, belongs to, or is located within a specific commune (municipal administrative unit).
-
C.
isCoastalSettlementOf
Indicates that a settlement is located on or near the coast within the territory of a specified geographic or administrative area.
-
D.
hasCoastalMunicipalities
Indicates that a region or higher-level area includes one or more municipalities that are located along a sea or ocean coastline.
-
E.
hasCommunesNear
Indicates that one entity has communes located in its nearby geographic vicinity.
- F. None of above. chosen
Provenance (4 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60d8d749881909594e450462bca49 |
completed | May 2, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 26, 2026, 9:03 p.m.