Triple
T7106405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amity town council |
E165595
|
entity |
| Predicate | governingFunctions |
P3902
|
FINISHED |
| Object | public safety policy |
—
|
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: public safety policy | Statement: [Amity town council, governingFunctions, public safety policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingFunctions Context triple: [Amity town council, governingFunctions, public safety policy]
-
A.
governmentalFunction
chosen
Indicates that an entity performs, embodies, or is responsible for an official role, duty, or activity of a government.
-
B.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
C.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
D.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
-
E.
governingFramework
Indicates the overarching set of rules, principles, or standards that regulates, constrains, or guides how something operates or is carried out.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5b9f13c8190a14898f241ec17a4 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.