Triple
T7715795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murray River Council |
E174876
|
entity |
| Predicate | hasRiverFrontage |
P74732
|
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: [Murray River Council, hasRiverFrontage, Murray River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverFrontage Context triple: [Murray River Council, hasRiverFrontage, Murray River]
-
A.
hasWaterfrontArea
Indicates that an entity possesses or includes an area directly adjacent to or bordering a body of water.
-
B.
hasRiverfrontDistrict
chosen
Indicates that a place includes a designated district or area that directly borders and is oriented around a river.
-
C.
isWaterfrontBuilding
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
-
D.
coastalFrontageFor
Indicates that one entity has a boundary or frontage directly along the coast associated with another entity.
-
E.
hasIndustrialWaterfront
Indicates that an entity possesses or includes a waterfront area used for industrial purposes or activities.
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.