Triple
T32590261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seymour Narrows |
E833042
|
entity |
| Predicate | hasTidalRangeInfluenceFrom |
P139765
|
FINISHED |
| Object | Georgia Strait |
—
|
NE NERFINISHED |
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: Georgia Strait | Statement: [Seymour Narrows, hasTidalRangeInfluenceFrom, Georgia Strait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTidalRangeInfluenceFrom Context triple: [Seymour Narrows, hasTidalRangeInfluenceFrom, Georgia Strait]
-
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.
isTidalInfluenced
chosen
Indicates that an entity is affected or controlled by tidal forces or tidal conditions.
-
C.
isTidalMouthOf
Indicates that one location is the tidal mouth or estuarine outlet through which a river or watercourse enters a larger body of water.
-
D.
tideSystem
Indicates a relationship where a system is characterized by, governed by, or functionally organized around tidal phenomena or tidal forces.
-
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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 1, 2026, 1:05 a.m.