Triple
T17019214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotorua Lakes Council |
E412900
|
entity |
| Predicate | governsAreaKnownFor |
P125527
|
FINISHED |
| Object | geothermal activity |
—
|
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: geothermal activity | Statement: [Rotorua Lakes Council, governsAreaKnownFor, geothermal activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsAreaKnownFor Context triple: [Rotorua Lakes Council, governsAreaKnownFor, geothermal activity]
-
A.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
-
B.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
C.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
-
D.
governedTerritory
Indicates that one entity exercises political authority or control over another entity or geographic area as its governing power.
-
E.
areaOfAuthority
Indicates the domain, region, or scope within which an entity has official power, control, or responsibility.
- F. None of above. chosen
Provenance (4 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d481a0988190a13d0928e0c7ebbf |
completed | April 18, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:33 a.m.