Triple
T37220264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moorabool River |
E922857
|
entity |
| Predicate | nearbyLocalGovernmentArea |
P74637
|
FINISHED |
| Object | City of Greater Geelong |
—
|
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: City of Greater Geelong | Statement: [Moorabool River, nearbyLocalGovernmentArea, City of Greater Geelong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyLocalGovernmentArea Context triple: [Moorabool River, nearbyLocalGovernmentArea, City of Greater Geelong]
-
A.
localGovernmentAreaOf
chosen
Indicates that one entity is the local government area within whose jurisdiction or administrative boundaries the other entity is located.
-
B.
nearbyPoliticalEntity
Indicates that one political entity is geographically close to another political entity, without necessarily sharing a border.
-
C.
governingBodyNearby
Indicates that a governing body is located in close physical proximity to the referenced entity or area.
-
D.
nearbyGovernorate
Indicates that one governorate is geographically close to or adjacent to another governorate.
-
E.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 3, 2026, 4:15 p.m.