Triple
T1457945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wodonga |
E31440
|
entity |
| Predicate | riverFormsBorderBetween |
P224
|
FINISHED |
| Object | Victoria and New South Wales at Wodonga |
—
|
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: Victoria and New South Wales at Wodonga | Statement: [Wodonga, riverFormsBorderBetween, Victoria and New South Wales at Wodonga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverFormsBorderBetween Context triple: [Wodonga, riverFormsBorderBetween, Victoria and New South Wales at Wodonga]
-
A.
borderedBy
chosen
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
borderStraddling
Indicates that something (such as a feature, structure, or area) extends across and occupies territory on both sides of a border between two regions or jurisdictions.
-
C.
riverFeatureType
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
D.
locatedBetweenRivers
Indicates that something is situated in the area or region bounded or flanked by two rivers.
-
E.
riverConfluence
Indicates the location or relationship where two or more rivers or streams join and merge into a single watercourse.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59a462881908e84b27846a6bc04 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.