Triple
T32200026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Pierre-d’Oléron |
E822506
|
entity |
| Predicate | hasCoastalHeritage |
P75701
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Saint-Pierre-d’Oléron, hasCoastalHeritage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalHeritage Context triple: [Saint-Pierre-d’Oléron, hasCoastalHeritage, yes]
-
A.
hasHeritageCoastStatus
Indicates that a coastal area has been officially designated as a Heritage Coast, recognizing its special natural, scenic, or environmental value.
-
B.
hasMaritimeHeritage
Indicates that an entity possesses a historical, cultural, or traditional connection to maritime activities, seafaring, or the sea.
-
C.
hasCoastalCharacteristic
chosen
Indicates that an entity possesses a feature, quality, or condition specifically related to coastal or shoreline environments.
-
D.
hasCoastalLandmarks
Indicates that an entity possesses or is associated with notable geographic or cultural features located along a coast.
-
E.
hasCoastalSection
Indicates that a geographic entity includes at least one section of land that directly borders a sea or ocean.
- F. None of above.
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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:36 a.m.