Triple
T12292552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crosby Landing Beach |
E292997
|
entity |
| Predicate | hasTideCondition |
P4652
|
FINISHED |
| Object | large tidal range |
—
|
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: large tidal range | Statement: [Crosby Landing Beach, hasTideCondition, large tidal range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTideCondition Context triple: [Crosby Landing Beach, hasTideCondition, large tidal range]
-
A.
hasTidalRange
chosen
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
B.
tideType
Indicates the specific category or phase of the tide (such as high, low, rising, or falling) associated with a given tidal event or condition.
-
C.
hasSeaCondition
Indicates that an entity is associated with or characterized by a particular state or condition of the sea.
-
D.
containsTidalFeatures
Indicates that one entity exhibits observable tidal features caused by gravitational interactions with another entity.
-
E.
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.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d22ba488190914342fa7e69e159 |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c4ec6c4819085880bdefdd0f354 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.