Triple
T19061936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Greater Geelong |
E466552
|
entity |
| Predicate | hasSuburbClassification |
P36805
|
FINISHED |
| Object | urban |
—
|
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: urban | Statement: [City of Greater Geelong, hasSuburbClassification, urban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuburbClassification Context triple: [City of Greater Geelong, hasSuburbClassification, urban]
-
A.
isResidentialSuburbOf
Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
-
B.
containsSuburbs
Indicates that a larger geographic area or administrative region includes one or more suburbs within its boundaries.
-
C.
hasTypeOfSubdivision
chosen
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
D.
isCommercialSuburbOf
Indicates that one area functions primarily as a business or commercial district that is part of, or subordinate to, a larger urban area or city.
-
E.
hasMajorSuburb
Indicates that a larger urban area includes or is associated with a specific major suburb within its boundaries or sphere.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e194c854819085a0a48d22c5cebd |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.