Triple
T37685394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Regent River |
E938352
|
entity |
| Predicate | hasCatchmentRegion |
P164992
|
FINISHED |
| Object | northwest Kimberley |
—
|
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: northwest Kimberley | Statement: [Prince Regent River, hasCatchmentRegion, northwest Kimberley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatchmentRegion Context triple: [Prince Regent River, hasCatchmentRegion, northwest Kimberley]
-
A.
hasCatchmentArea
Indicates that a geographic or administrative unit serves as the area from which an entity (such as a facility or service) draws its users, resources, or influence.
-
B.
hasCatchmentAreaLocation
chosen
Indicates that a catchment area is geographically located in or associated with a specific place or region.
-
C.
hasCatchmentAuthority
Indicates that an entity holds official responsibility or authority over managing and regulating a particular catchment area.
-
D.
includesCatchmentOf
Indicates that one area or region fully contains the catchment area or drainage basin of another.
-
E.
isInCatchment
Indicates that one entity lies within the geographic or service area covered or served by another 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
Created at: May 3, 2026, 4:18 p.m.