Triple
T7258789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bendigo |
E159590
|
entity |
| Predicate | hasRiverOrCreek |
P165
|
FINISHED |
| Object | Bendigo Creek |
—
|
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: Bendigo Creek | Statement: [Bendigo, hasRiverOrCreek, Bendigo Creek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverOrCreek Context triple: [Bendigo, hasRiverOrCreek, Bendigo Creek]
-
A.
hasRiver
chosen
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
B.
hasRiverActivity
Indicates that an entity engages in, supports, or is associated with activities occurring on or along a river.
-
C.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
D.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
E.
hasTownOnRiver
Indicates that a town is situated on or directly adjacent to a particular river.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:57 p.m.