Triple
T20729438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echuca railway line |
E509529
|
entity |
| Predicate | followsRiverTo |
P3624
|
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: [Echuca railway line, followsRiverTo, Murray River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsRiverTo Context triple: [Echuca railway line, followsRiverTo, Murray River]
-
A.
followsWatercourse
chosen
Indicates that one entity runs alongside or traces the path of a watercourse such as a river, stream, or canal.
-
B.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
C.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
-
D.
mentionsRiver
Indicates that an entity refers to or brings up a river in some form of content or communication.
-
E.
hasRiverBelow
Indicates that one entity is located above another such that a river lies physically below it.
- 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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1eb5d44819082d9fa410e676d91 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:30 p.m.