Triple
T11846785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peel-Harvey Estuary |
E281797
|
entity |
| Predicate | tidalConnection |
P88668
|
FINISHED |
| Object | tidally influenced |
—
|
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: tidally influenced | Statement: [Peel-Harvey Estuary, tidalConnection, tidally influenced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tidalConnection Context triple: [Peel-Harvey Estuary, tidalConnection, tidally influenced]
-
A.
hasTidalConnection
chosen
Indicates that one entity is linked to another through the movement, influence, or exchange of tidal waters.
-
B.
tidalLock
Indicates that one astronomical body always shows the same face to another because its rotational period matches its orbital period around that body.
-
C.
isTidal
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
D.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
E.
ridgeConnection
Indicates a structural relationship where one ridge is connected or linked to another ridge, forming a continuous or associated ridge feature.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65b5ff08190bb58361f6a6acdca |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.