Triple
T8658570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geelong |
E205485
|
entity |
| Predicate | hasSuburbStatus |
P60379
|
FINISHED |
| Object | central suburb of Greater Geelong urban area |
—
|
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: central suburb of Greater Geelong urban area | Statement: [Geelong, hasSuburbStatus, central suburb of Greater Geelong urban area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuburbStatus Context triple: [Geelong, hasSuburbStatus, central suburb of Greater Geelong urban area]
-
A.
containsSuburbs
Indicates that a larger geographic area or administrative region includes one or more suburbs within its boundaries.
-
B.
hasNeighbourhoodStatus
chosen
Indicates that an entity has a particular status, classification, or condition specifically in relation to a given neighbourhood.
-
C.
hasSuburbAlong
Indicates that a larger area or route is associated with, or passes by, one or more suburbs located along its extent.
-
D.
isResidentialSuburbOf
Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
-
E.
hasNearbySuburb
Indicates that one location has another location as a suburb situated in close geographic proximity.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc486ece68819089c74bdf98b64490 |
completed | March 31, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:30 p.m.