Triple
T25677330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lihou headland |
E643842
|
entity |
| Predicate | isTidalContext |
P159482
|
FINISHED |
| Object | associated with tidal island access |
—
|
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: associated with tidal island access | Statement: [Lihou headland, isTidalContext, associated with tidal island access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTidalContext Context triple: [Lihou headland, isTidalContext, associated with tidal island access]
-
A.
isTidal
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
B.
hasTidalConnection
Indicates that one entity is linked to another through the movement, influence, or exchange of tidal waters.
-
C.
hasTidalRace
Indicates that a location or waterway experiences a strong, fast-moving tidal current or rapid flow caused by tidal changes.
-
D.
isOnTidalIsland
Indicates that something is located on a tidal island, i.e., land connected to the mainland at low tide and isolated by water at high tide.
-
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. chosen
Provenance (4 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb3712cc8190b6e851960cc7c9e9 |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 7:41 p.m.