Triple
T24547334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorta Yorta |
E607260
|
entity |
| Predicate | hasRiverConnection |
P165
|
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: [Yorta Yorta, hasRiverConnection, Murray River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverConnection Context triple: [Yorta Yorta, hasRiverConnection, Murray River]
-
A.
hydrologicallyConnectedTo
Indicates that two water bodies or hydrological features are linked such that water can flow or be transferred between them, directly or indirectly, through the hydrological system.
-
B.
hasRiver
chosen
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
hasRiverCounterpart
Indicates that one entity has a corresponding or analogous counterpart in the context of a river.
-
D.
hasTributaryRelationsWith
Indicates that one entity maintains a tributary relationship with another, typically involving regular payments or offerings in exchange for protection, favor, or acknowledgment of superiority.
-
E.
hasRiverPortPotential
Indicates that a location has suitable conditions to support the development or operation of a river port.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8caba8c819082c3bf33b6ff9cd0 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.