Triple
T11426436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strymonian Gulf |
E270761
|
entity |
| Predicate | hasCoastlineUse |
P20797
|
FINISHED |
| Object | beach tourism |
—
|
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: beach tourism | Statement: [Strymonian Gulf, hasCoastlineUse, beach tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastlineUse Context triple: [Strymonian Gulf, hasCoastlineUse, beach tourism]
-
A.
hasShorelineUse
chosen
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
-
B.
hasCoastlineType
Indicates the specific nature or classification of the coastline associated with a geographic entity.
-
C.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
D.
hasCoastalSection
Indicates that a geographic entity includes at least one section of land that directly borders a sea or ocean.
-
E.
hasCoastlineDesignation
Indicates that a geographic area’s coastline has been assigned a specific official classification or status.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c000b88190bfaa646b2dc424b7 |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.