Triple
T35798384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darling sub-basin |
E1034897
|
entity |
| Predicate | containsCatchmentOf |
P127974
|
FINISHED |
| Object | Darling River |
—
|
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: Darling River | Statement: [Darling sub-basin, containsCatchmentOf, Darling River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCatchmentOf Context triple: [Darling sub-basin, containsCatchmentOf, Darling River]
-
A.
includesCatchmentOf
chosen
Indicates that one area or region fully contains the catchment area or drainage basin of another.
-
B.
isInCatchment
Indicates that one entity lies within the geographic or service area covered or served by another entity.
-
C.
hasCatchmentAuthority
Indicates that an entity holds official responsibility or authority over managing and regulating a particular catchment area.
-
D.
containsTributariesOf
Indicates that one water body or drainage system includes within it the tributary streams or rivers of another.
-
E.
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.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00d08e8fac8190b59359134e6e1c03 |
completed | May 10, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_6a00d0127c088190a6f5b360450af113 |
completed | May 10, 2026, 6:36 p.m. |
Created at: May 3, 2026, 4:06 p.m.