Triple
T25351603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albury–Wodonga cross-border region |
E635700
|
entity |
| Predicate | riverFormsBoundary |
P31306
|
FINISHED |
| Object | Murray 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: Murray River | Statement: [Albury–Wodonga cross-border region, riverFormsBoundary, Murray River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverFormsBoundary Context triple: [Albury–Wodonga cross-border region, riverFormsBoundary, Murray River]
-
A.
riverFormsBorderWith
chosen
Indicates that a river serves as a boundary line between two geographic or political entities.
-
B.
formsBoundaryType
Indicates that one entity serves as a specific type of boundary for another entity.
-
C.
formsShorelineOf
Indicates that one geographic feature constitutes or defines the boundary or edge (shoreline) of a body of water.
-
D.
outerBoundary
Indicates that one entity serves as the enclosing outer limit or perimeter that bounds another entity or region.
-
E.
easternBoundaryFormedBy
Indicates that the eastern boundary of an area, region, or object is defined or formed by a specified feature or 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:34 p.m.