Triple
T13548659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freshwater Parish Council |
E323581
|
entity |
| Predicate | mayManage |
P24644
|
FINISHED |
| Object | local allotments in Freshwater |
—
|
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 allotments in Freshwater | Statement: [Freshwater Parish Council, mayManage, local allotments in Freshwater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayManage Context triple: [Freshwater Parish Council, mayManage, local allotments in Freshwater]
-
A.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
B.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
-
C.
manageThrough
Indicates that one entity exercises control, direction, or administration over another entity or process by means of an intermediary entity, channel, or mechanism.
-
D.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
-
E.
hasManagement
chosen
Indicates that one entity exercises managerial authority or oversight over another entity.
- 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.