Triple
T31855360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Currumbin Creek catchment |
E813179
|
entity |
| Predicate | hasWaterFlow |
P137958
|
FINISHED |
| Object | perennial streamflow |
—
|
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: perennial streamflow | Statement: [Currumbin Creek catchment, hasWaterFlow, perennial streamflow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterFlow Context triple: [Currumbin Creek catchment, hasWaterFlow, perennial streamflow]
-
A.
hasWaterMovement
chosen
Indicates that one entity exhibits or is characterized by a particular type or pattern of water movement.
-
B.
hasWaterAvailability
Indicates that an entity has access to or is supplied with a certain amount or level of water.
-
C.
waterFlowsThrough
Indicates that water moves along a path or channel passing from one location or object to another.
-
D.
hasWaterFunction
Indicates that an entity performs, provides, or is associated with a specific function or role related to water.
-
E.
hasWaterUse
Indicates a relationship where one entity utilizes or consumes water for a particular purpose, process, or function.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 30, 2026, 11:52 p.m.