Triple
T20366184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avon Valley |
E496914
|
entity |
| Predicate | upperCatchmentOf |
P127974
|
FINISHED |
| Object | Swan 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: Swan River | Statement: [Avon Valley, upperCatchmentOf, Swan River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperCatchmentOf Context triple: [Avon Valley, upperCatchmentOf, Swan River]
-
A.
upstreamRiver
Indicates that one river is located or flows in an upstream direction relative to another river within the same watercourse system.
-
B.
countryOfUpperCourse
Indicates the country through which the upper (initial) part of a river’s course flows.
-
C.
includesCatchmentOf
chosen
Indicates that one area or region fully contains the catchment area or drainage basin of another.
-
D.
knownAsInUpperCourse
Indicates that a river or watercourse is referred to by a particular name specifically along its upper course or upstream section.
-
E.
upstreamDam
Indicates that one entity is located or positioned upstream of another entity in relation to a dam, typically affecting or influenced by the dam’s presence or operation.
- 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67871bfdc8190948c46497cd675c9 |
completed | April 20, 2026, 7:03 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:26 a.m.