Triple
T35630453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local government areas of Tasmania |
E1029569
|
entity |
| Predicate | includesLGA |
P207074
|
FINISHED |
| Object | City of Hobart |
E15892
|
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: City of Hobart | Statement: [Local government areas of Tasmania, includesLGA, City of Hobart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLGA Context triple: [Local government areas of Tasmania, includesLGA, City of Hobart]
-
A.
includesDistrict
Indicates that one administrative or geographic entity contains or encompasses a specific district within its boundaries.
-
B.
includesMetropolitanZone
Indicates that one geographic or administrative area contains or encompasses a designated metropolitan zone within its boundaries.
-
C.
includesMajorMetropolitanArea
Indicates that one entity geographically contains or encompasses a major metropolitan area within its boundaries.
-
D.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
-
E.
includesMetropolitanDivision
Indicates that one administrative or statistical area contains a specific metropolitan division as a component part of its overall territory or structure.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfae8d3c819087b14c2e1c81f472 |
completed | June 23, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:05 p.m.