Triple
T31660191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heathcote County Council |
E807977
|
entity |
| Predicate | absorbedFunction |
P30941
|
FINISHED |
| Object | local infrastructure management |
—
|
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: local infrastructure management | Statement: [Heathcote County Council, absorbedFunction, local infrastructure management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: absorbedFunction Context triple: [Heathcote County Council, absorbedFunction, local infrastructure management]
-
A.
absorbed
chosen
Indicates that one entity takes in, soaks up, or assimilates another entity or substance.
-
B.
associatedFunction
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
C.
affectedFunction
Indicates that one entity has an impact on, alters, or impairs the operation or behavior of another entity’s function.
-
D.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an entity.
-
E.
artifactFunction
Indicates that an artifact is used for, designed for, or serves a particular function or purpose.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:56 p.m.