Triple
T36807914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Arm |
E909505
|
entity |
| Predicate | locatedInHinterlandOf |
P205062
|
FINISHED |
| Object | Byron Bay |
E52272
|
NE 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: Byron Bay | Statement: [Main Arm, locatedInHinterlandOf, Byron Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInHinterlandOf Context triple: [Main Arm, locatedInHinterlandOf, Byron Bay]
-
A.
locatedInland
Indicates that something is situated away from the coast or shoreline, within the interior of a land area.
-
B.
situatedAmong
Indicates that an entity is located within or surrounded by multiple other entities in its immediate environment.
-
C.
locatedInHills
Indicates that something is situated within or among hilly terrain or a region characterized by hills.
-
D.
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.
-
E.
locatedInMountainRainShadowOf
Indicates that one location lies in the rain shadow of a mountain or mountain range, receiving reduced precipitation because the mountains block prevailing moisture-bearing winds.
- F. None of above. chosen
Provenance (5 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3d17b499c48190b3e47dfea2b6ad79 |
completed | June 25, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.