Triple

T12209166
Position Surface form Disambiguated ID Type / Status
Subject Middleton Parish Council E290910 entity
Predicate canOrganise P123 FINISHED
Object community events in 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: community events in Middleton | Statement: [Middleton Parish Council, canOrganise, community events in Middleton]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canOrganise
Context triple: [Middleton Parish Council, canOrganise, community events in Middleton]
  • A. organisedFor
    Indicates that something has been arranged, structured, or coordinated specifically to serve, support, or benefit a particular entity or purpose.
  • B. organizes chosen
    Indicates that one entity arranges, coordinates, or structures activities, items, or people into an ordered or planned form for a particular purpose.
  • C. canBeTaskOrganizedWith
    Indicates that one entity can be grouped, scheduled, or managed together with another as part of the same task or workflow.
  • D. organizedAt
    Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
  • E. canBeArrangedFor
    Indicates that one entity is able to be scheduled, organized, or set up on behalf of or for the benefit of 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_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.