Triple
T29590652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darnley Island |
E754145
|
entity |
| Predicate | adminRegionType |
P62377
|
FINISHED |
| Object | local government area |
—
|
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: local government area | Statement: [Darnley Island, adminRegionType, local government area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminRegionType Context triple: [Darnley Island, adminRegionType, local government area]
-
A.
exportRegion
Indicates the region or geographic area from which goods, services, or resources are exported.
-
B.
regionalType
Indicates the classification of a region according to its designated type or category within a broader geographic or administrative system.
-
C.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
D.
politicalRegionType
chosen
Indicates the classification of a political region according to its governmental or administrative type (e.g., state, province, municipality).
-
E.
typicalRegionType
Indicates that a region is of a characteristic or commonly occurring type for a given context or entity.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 28, 2026, 6:13 p.m.