Triple
T10552094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brockville City Council |
E248976
|
entity |
| Predicate | hasPolicyFunction |
P94643
|
FINISHED |
| Object | setting local policies |
—
|
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: setting local policies | Statement: [Brockville City Council, hasPolicyFunction, setting local policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolicyFunction Context triple: [Brockville City Council, hasPolicyFunction, setting local policies]
-
A.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
-
B.
hasPolicyStatus
Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
-
C.
hasAccessFunction
Indicates that one entity is associated with a function or mechanism that enables access to another entity or resource.
-
D.
hasKeyPolicy
Indicates that an entity is associated with a specific key management or access control policy governing how its keys may be used or managed.
-
E.
hasReferencePolicy
Indicates that an entity is governed by or associated with a specific reference policy that defines how it should be used, accessed, or managed.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d52710869c81909b6db1a190825bad |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
| PDg | Predicate description generation | batch_69d5270eca0481908573b698390c5b08 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:34 p.m.