Triple
T35595859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenah Valley |
E1028628
|
entity |
| Predicate | locationDirectionInCity |
P82745
|
FINISHED |
| Object | north-west of Hobart CBD |
—
|
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: north-west of Hobart CBD | Statement: [Lenah Valley, locationDirectionInCity, north-west of Hobart CBD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationDirectionInCity Context triple: [Lenah Valley, locationDirectionInCity, north-west of Hobart CBD]
-
A.
locationDirection
Indicates that one entity is located in a specific directional relation (such as north, south, above, or below) relative to another entity.
-
B.
directionWithinCity
chosen
Indicates a directional relationship specifying where something is located or oriented within the boundaries of a particular city.
-
C.
routeDirectionB
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
D.
directionOptions
Indicates the possible directions or orientations that can be chosen or assigned within a given context or relationship.
-
E.
routeDirectionA
Indicates the primary or first directional orientation or heading associated with a specific route.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.