Triple
T18456573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton North |
E450915
|
entity |
| Predicate | hasNeighbouringAreaType |
P6822
|
FINISHED |
| Object | inner-city suburb |
—
|
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: inner-city suburb | Statement: [Hamilton North, hasNeighbouringAreaType, inner-city suburb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighbouringAreaType Context triple: [Hamilton North, hasNeighbouringAreaType, inner-city suburb]
-
A.
hasAreaType
chosen
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
B.
hasNeighboringZone
Indicates that one zone is directly adjacent to or shares a boundary with another zone.
-
C.
hasNeighbouringProtectedArea
Indicates that one protected area is directly adjacent to or shares a boundary with another protected area.
-
D.
hasNearbyLandscapeType
Indicates that one entity is located close to, or in the vicinity of, a particular type of landscape.
-
E.
hasNeighbouringLocality
Indicates that one locality is geographically adjacent to or directly borders another locality.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5264ce5948190b57baa2ea71297a9 |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.