Triple
T21346463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subiaco Creek |
E526350
|
entity |
| Predicate | catchmentType |
P49162
|
FINISHED |
| Object | urban catchment |
—
|
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: urban catchment | Statement: [Subiaco Creek, catchmentType, urban catchment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catchmentType Context triple: [Subiaco Creek, catchmentType, urban catchment]
-
A.
watershedType
chosen
Indicates the classification or category of a watershed associated with an entity (e.g., by hydrologic, ecological, or management type).
-
B.
reservoirCatchment
Indicates that one entity is the catchment area that drains water into a specified reservoir.
-
C.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
D.
isInCatchment
Indicates that one entity lies within the geographic or service area covered or served by another entity.
-
E.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee5ba8f1c8819089c5d753876b44d5 |
completed | April 26, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:55 p.m.