Triple
T36808071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pocket |
E909509
|
entity |
| Predicate | isInHinterlandOf |
P52232
|
FINISHED |
| Object | Byron Bay |
—
|
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: Byron Bay | Statement: [The Pocket, isInHinterlandOf, Byron Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInHinterlandOf Context triple: [The Pocket, isInHinterlandOf, Byron Bay]
-
A.
isLocatedOnOutskirtsOf
Indicates that one entity is situated on the outer edge or peripheral area of another entity, rather than in its central or inner part.
-
B.
isInteriorTownOf
Indicates that one town is located within the interior region of, and is administratively or geographically associated with, a larger area or jurisdiction.
-
C.
hasRuralHinterland
chosen
Indicates that a place or urban area is associated with and served by a surrounding rural region that supports it economically, socially, or functionally.
-
D.
isInBorderTown
Indicates that an entity is located in a town situated on or very near a political or geographic border.
-
E.
isInlandFrom
Indicates that one place lies away from the coast, further toward the interior of the land, relative to another place.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca93bd0481909d6eee9e950001a1 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.