Triple
T14167147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reversing Falls |
E351109
|
entity |
| Predicate | waterFlowDirectionChangesDueTo |
P75396
|
FINISHED |
| Object | tidal forces |
—
|
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: tidal forces | Statement: [Reversing Falls, waterFlowDirectionChangesDueTo, tidal forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterFlowDirectionChangesDueTo Context triple: [Reversing Falls, waterFlowDirectionChangesDueTo, tidal forces]
-
A.
waterExchangeThrough
Indicates a relationship where water is transferred or shared between entities through a specific medium, pathway, or mechanism.
-
B.
waterFlowRate
Indicates the rate at which water moves or is transported through a given point or system over time.
-
C.
waterwayDirection
chosen
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
-
D.
waterDivertedFrom
Indicates that water is intentionally redirected or channeled away from one source, path, or location to another.
-
E.
drainageDirection
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b355f08190864c7322bbcb766d |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1 a.m.