Triple
T34449781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waipa District Council |
E884329
|
entity |
| Predicate | hasAnnualPlan |
P10988
|
FINISHED |
| Object | Waipa District Council Annual Plan |
—
|
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: Waipa District Council Annual Plan | Statement: [Waipa District Council, hasAnnualPlan, Waipa District Council Annual Plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnnualPlan Context triple: [Waipa District Council, hasAnnualPlan, Waipa District Council Annual Plan]
-
A.
isAnnual
Indicates that something occurs, is scheduled, or is valid once every year.
-
B.
hasAnnualList
Indicates that an entity maintains or is associated with a list that is updated or issued on an annual basis.
-
C.
hasPlan
chosen
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
D.
hasAnnualFee
Indicates that an entity (such as a product, service, or account) requires the payment of a recurring fee on an annual basis.
-
E.
hasBasePlan
Indicates that an entity is associated with or derived from a specified foundational or default plan.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 2 a.m.