Triple
T35022192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Googong |
E1010225
|
entity |
| Predicate | hasNearbyWaterResource |
P49291
|
FINISHED |
| Object | Googong Dam |
—
|
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: Googong Dam | Statement: [Googong, hasNearbyWaterResource, Googong Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyWaterResource Context triple: [Googong, hasNearbyWaterResource, Googong Dam]
-
A.
hasNearbyWater
chosen
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
B.
hasNearbyWaterInfrastructure
Indicates that a location or entity is situated close to water-related infrastructure such as pipes, treatment facilities, or distribution systems.
-
C.
hasWaterResourceRole
Indicates that an entity participates in a water-related resource context with a specified functional role (e.g., source, user, manager, or regulator of water resources).
-
D.
hasWaterResourceType
Indicates that an entity is associated with a specific type or category of water resource.
-
E.
hasNearbyWaterBoard
Indicates that an entity is located close to, or within the jurisdictional area of, a water management or water regulatory board.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: May 3, 2026, 4:01 p.m.