Triple
T20482065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merungle Hill |
E502479
|
entity |
| Predicate | isInMurrayDarlingBasin |
P18951
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Merungle Hill, isInMurrayDarlingBasin, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInMurrayDarlingBasin Context triple: [Merungle Hill, isInMurrayDarlingBasin, true]
-
A.
locatedInBasin
chosen
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
-
B.
isInCatchment
Indicates that one entity lies within the geographic or service area covered or served by another entity.
-
C.
hasSettlementInBasin
Indicates that a settlement is located within the geographic area of a specific basin.
-
D.
basinState
Indicates that a state contains or encompasses the drainage basin or watershed of a particular river or water system.
-
E.
hasHeadwatersIn
Indicates that the source or origin of a river, stream, or similar watercourse is located within a specified geographic area or feature.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b57fa9c819091d12320d46a0cee |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:34 a.m.