Triple
T17273102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glennies Creek Dam |
E419313
|
entity |
| Predicate | supportsTownWaterSupplyFor |
P4360
|
FINISHED |
| Object | communities in the Hunter Region |
—
|
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: communities in the Hunter Region | Statement: [Glennies Creek Dam, supportsTownWaterSupplyFor, communities in the Hunter Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTownWaterSupplyFor Context triple: [Glennies Creek Dam, supportsTownWaterSupplyFor, communities in the Hunter Region]
-
A.
sourceOfWaterSupply
chosen
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
B.
waterSupplyShare
Indicates the proportion of a total water supply that is allocated to or used by a particular entity.
-
C.
waterSupplySystemCompletedIn
Indicates that the construction or establishment of a water supply system was completed in a specified time or place.
-
D.
hasWaterTown
Indicates that one place is a town characterized by or associated with water in relation to another entity.
-
E.
managesWaterFrom
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4b023c8190b92df4015c14c3a8 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.