Triple
T2962222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluemull Sound |
E80074
|
entity |
| Predicate | hasTidalResource |
P11760
|
FINISHED |
| Object | strong tidal currents |
—
|
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: strong tidal currents | Statement: [Bluemull Sound, hasTidalResource, strong tidal currents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTidalResource Context triple: [Bluemull Sound, hasTidalResource, strong tidal currents]
-
A.
isTidal
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
B.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
C.
hasWatershed
Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
-
D.
hasMarineResource
chosen
Indicates that one entity possesses, contains, or is associated with a marine (ocean or sea-based) resource in relation to another entity.
-
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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9955e6488190bea170724d5fbfe8 |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.