Triple
T3386382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namoi River catchment |
E71311
|
entity |
| Predicate | hasWaterResourceType |
P47163
|
FINISHED |
| Object | surface water |
—
|
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: surface water | Statement: [Namoi River catchment, hasWaterResourceType, surface water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterResourceType Context triple: [Namoi River catchment, hasWaterResourceType, surface water]
-
A.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
B.
hasWatershed
Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
-
C.
hasHydrosphere
Indicates that an entity possesses or is characterized by a surrounding layer or system of water, such as oceans, seas, lakes, or other bodies of liquid water.
-
D.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
E.
hasWatershedCharacteristic
Indicates that a watershed possesses a specified characteristic, feature, or property.
- F. None of above. chosen
Provenance (4 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb662d190819085b211dac85a83b2 |
completed | March 8, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69ada43615f08190ac2275020d157983 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada527ff308190813a7ffdcdec4322 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:14 p.m.