Triple
T31333997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holm of Huip (tidal access) |
E799114
|
entity |
| Predicate | hasTidalAccess |
P1735
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Holm of Huip (tidal access), hasTidalAccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTidalAccess Context triple: [Holm of Huip (tidal access), hasTidalAccess, true]
-
A.
hasTidalConnection
Indicates that one entity is linked to another through the movement, influence, or exchange of tidal waters.
-
B.
isTidal
chosen
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
C.
isTidalContext
Indicates that the situation or environment is influenced by, related to, or occurring within tidal conditions or tidal cycles.
-
D.
hasTidalRace
Indicates that a location or waterway experiences a strong, fast-moving tidal current or rapid flow caused by tidal changes.
-
E.
hasTidalConstituent
Indicates that something includes or is associated with a specific tidal constituent as part of its tidal characteristics or behavior.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 29, 2026, 9:16 p.m.