Triple
T33923230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dipton |
E869672
|
entity |
| Predicate | governedByRegionalCouncil |
P129306
|
FINISHED |
| Object | Environment Southland |
—
|
NE NERFINISHED |
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: Environment Southland | Statement: [Dipton, governedByRegionalCouncil, Environment Southland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedByRegionalCouncil Context triple: [Dipton, governedByRegionalCouncil, Environment Southland]
-
A.
containsRegionalCouncil
Indicates that one administrative or geographic entity includes a regional council within its jurisdiction or boundaries.
-
B.
locatedInRegionalCouncil
chosen
Indicates that one entity is geographically situated within the jurisdictional area governed by a specific regional council.
-
C.
hasCountyCouncil
Indicates that an entity is administratively governed or overseen by a specific county council.
-
D.
governedByMultipleLocalAuthorities
Indicates that an entity falls under the jurisdiction or control of more than one local governing authority at the same time.
-
E.
hasLocalCouncilArea
Indicates that an entity is located within, or is administratively governed by, a specific local council area.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00bcfed6448190b2e816bbe7c61c55 |
completed | May 10, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_6a00bc7be24c81908ba5c1957edd2c10 |
completed | May 10, 2026, 5:12 p.m. |
Created at: May 1, 2026, 1:49 a.m.