Triple
T35624866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilltops local government area |
E1029420
|
entity |
| Predicate | LGARegionClassification |
P26631
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Hilltops local government area, LGARegionClassification, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LGARegionClassification Context triple: [Hilltops local government area, LGARegionClassification, regional]
-
A.
regionClassification
chosen
Indicates how a given area or location is categorized into a specific region based on defined criteria or boundaries.
-
B.
longitudeRegion
Indicates that an entity is located within or associated with a specific longitudinal region on the Earth’s surface.
-
C.
ISORegion
Indicates a standardized geographic or administrative region as defined by an ISO (International Organization for Standardization) code.
-
D.
geographicalRegionType
Indicates the specific kind or category of geographical region that an entity belongs to (e.g., continent, country, province, or city).
-
E.
regionalGrouping
Indicates that entities are organized or associated together based on shared geographic or regional characteristics.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ef4a5f481909f3241a4e20ea37e |
completed | May 3, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.