Triple
T27129531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randwick City Council |
E681524
|
entity |
| Predicate | hasCoastalSuburbs |
P15843
|
FINISHED |
| Object | Coogee |
—
|
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: Coogee | Statement: [Randwick City Council, hasCoastalSuburbs, Coogee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalSuburbs Context triple: [Randwick City Council, hasCoastalSuburbs, Coogee]
-
A.
isCoastalCitySuburb
Indicates that a suburb is located within or adjacent to a city that lies on a coastline, functioning as a suburban area of that coastal city.
-
B.
isCoastalProximitySuburbOf
Indicates that one suburb is located near the coast and is considered a suburban area associated with a particular primary locality or city.
-
C.
isCoastalCityNeighbourhood
Indicates that a neighborhood is located within a city that lies along a sea, ocean, or other significant coastal body of water.
-
D.
hasSuburbanAreas
chosen
Indicates that a place includes or is associated with surrounding residential suburban districts or neighborhoods.
-
E.
isCoastalResidentialAreaOf
Indicates that a residential area is located along or near the coast of a specified geographic or administrative 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: April 27, 2026, 9:03 a.m.