Triple
T25989347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tooma River |
E646299
|
entity |
| Predicate | hasWaterDiversion |
P119912
|
FINISHED |
| Object | Tooma–Tumut Tunnel |
—
|
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: Tooma–Tumut Tunnel | Statement: [Tooma River, hasWaterDiversion, Tooma–Tumut Tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterDiversion Context triple: [Tooma River, hasWaterDiversion, Tooma–Tumut Tunnel]
-
A.
waterDivertedFrom
Indicates that water is intentionally redirected or channeled away from one source, path, or location to another.
-
B.
waterDivertedThrough
chosen
Indicates that the flow of water is intentionally redirected from its original course to pass through a specified structure, channel, or location.
-
C.
riverDivertedTo
Indicates that the natural course of a river has been intentionally redirected from its original path to a new channel or destination.
-
D.
hasWaterManagementStructure
Indicates that one entity possesses, contains, or is associated with a built feature used to control, store, convey, or manage water.
-
E.
riverbedDivertedTo
Indicates that the natural course of a riverbed has been redirected or channeled toward another location or pathway.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 22, 2026, 8:55 a.m.