Triple
T31537040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weweantic River |
E804633
|
entity |
| Predicate | isTidalNear |
P171943
|
FINISHED |
| Object | its mouth |
—
|
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: its mouth | Statement: [Weweantic River, isTidalNear, its mouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTidalNear Context triple: [Weweantic River, isTidalNear, its mouth]
-
A.
isTidal
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
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.
isTidalInfluenced
Indicates that an entity is affected or controlled by tidal forces or tidal conditions.
-
D.
hasTidalConstituent
Indicates that something includes or is associated with a specific tidal constituent as part of its tidal characteristics or behavior.
-
E.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
- F. None of above. chosen
Provenance (4 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:04 p.m.