Triple
T12209164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middleton Parish Council |
E290910
|
entity |
| Predicate | canConsultOn |
P13956
|
FINISHED |
| Object | planning applications affecting Middleton |
—
|
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: planning applications affecting Middleton | Statement: [Middleton Parish Council, canConsultOn, planning applications affecting Middleton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canConsultOn Context triple: [Middleton Parish Council, canConsultOn, planning applications affecting Middleton]
-
A.
consultsOn
chosen
Indicates that one entity provides expert advice, guidance, or professional input to another entity regarding a specific subject, project, or decision.
-
B.
consulted
Indicates that one entity sought advice, information, or guidance from another entity.
-
C.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
D.
requiresConsultationWith
Indicates that performing an action or making a decision depends on first obtaining input, approval, or advice from a specified party.
-
E.
canLiaiseWith
Indicates that one entity is able or permitted to communicate and coordinate directly with another entity for collaboration or information exchange.
- 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.