Triple
T34555011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Beach |
E887178
|
entity |
| Predicate | hasForeshoreType |
P13817
|
FINISHED |
| Object | rocky foreshore |
—
|
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 foreshore | Statement: [Rocky Beach, hasForeshoreType, rocky foreshore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasForeshoreType Context triple: [Rocky Beach, hasForeshoreType, rocky foreshore]
-
A.
hasForeshoreReserve
Indicates that an entity possesses or is associated with a designated foreshore reserve area along a shoreline or coastal zone.
-
B.
shoreType
chosen
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
C.
propertyTypeAlongShore
Indicates the type or classification of a property specifically in relation to its location along a shoreline.
-
D.
hasShorelineUse
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
-
E.
hasShoreFeature
Indicates that a shore or coastline possesses a specific physical or environmental feature.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 1, 2026, 2:02 a.m.