Triple
T25208703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellevue Hill |
E631623
|
entity |
| Predicate | nearbyCommercialCentre |
P36605
|
FINISHED |
| Object | Bondi Junction |
—
|
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: Bondi Junction | Statement: [Bellevue Hill, nearbyCommercialCentre, Bondi Junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyCommercialCentre Context triple: [Bellevue Hill, nearbyCommercialCentre, Bondi Junction]
-
A.
nearbyUrbanCenter
chosen
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
B.
locationOfShoppingCenter
Indicates that a specified place is the geographic location where a particular shopping center is situated.
-
C.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
D.
nearbyEconomicActivity
Indicates that there is economic activity occurring in close physical proximity to the referenced entity.
-
E.
administrativeCentreNearby
Indicates that an administrative centre is located close to the referenced entity in geographic or spatial terms.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 12:57 p.m.