Triple
T12206827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coos Bay tidal flats |
E290856
|
entity |
| Predicate | hasTidalZone |
P57287
|
FINISHED |
| Object | intertidal zone |
—
|
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: intertidal zone | Statement: [Coos Bay tidal flats, hasTidalZone, intertidal zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTidalZone Context triple: [Coos Bay tidal flats, hasTidalZone, intertidal zone]
-
A.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
B.
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.
-
C.
containsTidalFeatures
chosen
Indicates that one entity exhibits observable tidal features caused by gravitational interactions with another entity.
-
D.
hasTidalConnection
Indicates that one entity is linked to another through the movement, influence, or exchange of tidal waters.
-
E.
isTidalMouthOf
Indicates that one location is the tidal mouth or estuarine outlet through which a river or watercourse enters a larger body of water.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.