Triple
T23947148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corin Dam |
E602943
|
entity |
| Predicate | partOfWaterSupplySystem |
P36984
|
FINISHED |
| Object | Canberra water supply system |
—
|
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: Canberra water supply system | Statement: [Corin Dam, partOfWaterSupplySystem, Canberra water supply system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfWaterSupplySystem Context triple: [Corin Dam, partOfWaterSupplySystem, Canberra water supply system]
-
A.
isPartOfWaterSystem
chosen
Indicates that one entity is a component, segment, or subsystem within a larger water distribution, treatment, or management system.
-
B.
sourceOfWaterSupply
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
C.
waterInfrastructure
Indicates the existence, development, or management of systems and facilities that supply, store, treat, or distribute water between entities.
-
D.
waterSupplyShare
Indicates the proportion of a total water supply that is allocated to or used by a particular entity.
-
E.
waterInfrastructureRole
Indicates the functional role or involvement an entity has in the provision, management, or operation of water infrastructure systems.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02ee0288190b58fd71b9cc65964 |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:17 p.m.