Triple

T27260822
Position Surface form Disambiguated ID Type / Status
Subject Lionacleit E687755 entity
Predicate hasSchoolRole P121011 FINISHED
Object serves Benbecula and surrounding islands 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: serves Benbecula and surrounding islands | Statement: [Lionacleit, hasSchoolRole, serves Benbecula and surrounding islands]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSchoolRole
Context triple: [Lionacleit, hasSchoolRole, serves Benbecula and surrounding islands]
  • A. schoolRole chosen
    Indicates the specific function, position, or capacity an entity holds within a school context (e.g., student, teacher, administrator).
  • B. hasSchool
    Indicates that an entity possesses, is associated with, or is served by a particular school.
  • C. hasSchoolIn
    Indicates that a school is located within or operates in a specified place or region.
  • D. hasSchoolCategory
    Indicates that an entity (such as a school or educational institution) is associated with a particular category or type of school.
  • E. hasSchoolsAccess
    Indicates that one entity has permission or the ability to access schools or school-related resources associated with 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_69ef3557abc481908bf3c146f0f3356a completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f6b49436b0819094e21603054d05d4 completed May 3, 2026, 2:36 a.m.
PD Predicate disambiguation batch_69f6b3a5fd8481909433e923c5e24e55 completed May 3, 2026, 2:32 a.m.
Created at: April 27, 2026, 10:52 a.m.