Triple
T34120268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avon River / Ōtākaro |
E875104
|
entity |
| Predicate | hasManagementProject |
P14971
|
FINISHED |
| Object | Ōtākaro Avon River Corridor regeneration |
—
|
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: Ōtākaro Avon River Corridor regeneration | Statement: [Avon River / Ōtākaro, hasManagementProject, Ōtākaro Avon River Corridor regeneration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManagementProject Context triple: [Avon River / Ōtākaro, hasManagementProject, Ōtākaro Avon River Corridor regeneration]
-
A.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
B.
hasProject
chosen
Indicates that an entity is associated with or responsible for a particular project.
-
C.
hasMaintenanceProjectsBy
Indicates that one entity is responsible for or associated with carrying out maintenance projects on another entity.
-
D.
hasManagementPlan
Indicates that an entity is associated with a defined management plan specifying how it should be overseen, maintained, or administered.
-
E.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a016b2629c48190befb10581560d58f |
completed | May 11, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a0167d5a2088190a68dbd2b87f73e80 |
completed | May 11, 2026, 5:23 a.m. |
Created at: May 1, 2026, 1:53 a.m.