Triple
T34449780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waipa District Council |
E884329
|
entity |
| Predicate | hasLongTermPlan |
P10988
|
FINISHED |
| Object | Waipa District Council Long-Term Plan |
—
|
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: Waipa District Council Long-Term Plan | Statement: [Waipa District Council, hasLongTermPlan, Waipa District Council Long-Term Plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongTermPlan Context triple: [Waipa District Council, hasLongTermPlan, Waipa District Council Long-Term Plan]
-
A.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
B.
hasPlan
chosen
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
C.
hasCentralPlan
Indicates that an entity is designed or organized according to a central, unified plan or layout.
-
D.
hasPlanningConcept
Indicates that an entity is associated with, defined by, or governed by a particular planning-related concept or framework.
-
E.
hasPlanningSignificance
Indicates that something holds importance or relevance for planning, decision-making, or future organizational activities.
- 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_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: May 1, 2026, 2 a.m.