Triple
T30219780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yurigahama sandbar |
E768309
|
entity |
| Predicate | tideCondition |
P66691
|
FINISHED |
| Object | low tide and spring tide |
—
|
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: low tide and spring tide | Statement: [Yurigahama sandbar, tideCondition, low tide and spring tide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tideCondition Context triple: [Yurigahama sandbar, tideCondition, low tide and spring tide]
-
A.
tideType
chosen
Indicates the specific category or phase of the tide (such as high, low, rising, or falling) associated with a given tidal event or condition.
-
B.
receivesTideFrom
Indicates that one entity obtains or is affected by tidal influence originating from another entity.
-
C.
tidalCurrentCharacteristic
Indicates the specific properties or behavior of a tidal current, such as its strength, direction, or variability.
-
D.
stormSurgeHeightLocation
Indicates the height of a storm surge measured at or associated with a specific location.
-
E.
isTidalInfluenced
Indicates that an entity is affected or controlled by tidal forces or tidal conditions.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff8bc9081909ad67eeac8291bf6 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:34 p.m.