Triple
T17985829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nerimbera Bridge |
E430228
|
entity |
| Predicate | riverBankProximity |
P130018
|
FINISHED |
| Object | downstream of Rockhampton city centre |
—
|
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: downstream of Rockhampton city centre | Statement: [Nerimbera Bridge, riverBankProximity, downstream of Rockhampton city centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverBankProximity Context triple: [Nerimbera Bridge, riverBankProximity, downstream of Rockhampton city centre]
-
A.
riverBankArea
Indicates the area of land adjacent to a riverbank associated with the given entity or location.
-
B.
riverBankTwo
Indicates a relationship where something is located on or associated with the second of two identified banks of a river.
-
C.
riverBankOnEastSide
Indicates that a river bank is located on the eastern side of a river or watercourse.
-
D.
nearbyRiverProject
Indicates that there is a project located close to or associated with a nearby river.
-
E.
riverBankOnSouthSide
Indicates that a river bank is located on the southern side of a specified river or watercourse.
- F. None of above. chosen
Provenance (4 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29b4e808190af06074168169035 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:23 a.m.