Triple
T10714294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Marija Bay |
E252620
|
entity |
| Predicate | hasShoreFeatures |
P6651
|
FINISHED |
| Object | rocky shoreline sections |
—
|
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: rocky shoreline sections | Statement: [Santa Marija Bay, hasShoreFeatures, rocky shoreline sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShoreFeatures Context triple: [Santa Marija Bay, hasShoreFeatures, rocky shoreline sections]
-
A.
hasShoreFeature
chosen
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
B.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
C.
hasMaritimeFeature
Indicates that one entity possesses, contains, or is characterized by a maritime-related feature such as a sea, coast, harbor, or other oceanic element.
-
D.
hasCoastalCharacteristic
Indicates that an entity possesses a feature, quality, or condition specifically related to coastal or shoreline environments.
-
E.
containsCoastalFeature
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6ff324d1881908b7cdf4ac208125f |
completed | April 9, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.