Triple
T13548662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freshwater Parish Council |
E323581
|
entity |
| Predicate | mayConsultOn |
P13956
|
FINISHED |
| Object | local planning applications |
—
|
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 planning applications | Statement: [Freshwater Parish Council, mayConsultOn, local planning applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayConsultOn Context triple: [Freshwater Parish Council, mayConsultOn, local planning applications]
-
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.
requiresConsultationWith
Indicates that performing an action or making a decision depends on first obtaining input, approval, or advice from a specified party.
-
C.
consulted
Indicates that one entity sought advice, information, or guidance from another entity.
-
D.
mayAdmit
Indicates that one entity has the permission or authority to allow another entity to enter, join, or be accepted into something.
-
E.
mayReportTo
Indicates that one entity is permitted or allowed to have a reporting relationship to another entity, such as an employee being allowed to report to a particular manager.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.