Triple
T12209157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middleton Parish Council |
E290910
|
entity |
| Predicate | mayLevy |
P41654
|
FINISHED |
| Object | parish precept |
—
|
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: parish precept | Statement: [Middleton Parish Council, mayLevy, parish precept]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayLevy Context triple: [Middleton Parish Council, mayLevy, parish precept]
-
A.
canLevy
chosen
Indicates that an entity has the authority or power to impose and collect a charge, tax, or fine on another entity or resource.
-
B.
mayHead
Indicates that an entity is permitted or eligible to serve as the leader or head of another entity.
-
C.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
D.
mayForm
Indicates that one entity has the potential or permission to be combined or configured to create, constitute, or result in another entity or structure.
-
E.
maySign
Indicates that an entity has the permission or authority to sign a document, agreement, or similar item.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.