Triple

T31043063
Position Surface form Disambiguated ID Type / Status
Subject Health Act 2004 E791047 entity
Predicate transfersFunctionsTo P196326 FINISHED
Object Health Service Executive NE NERFINISHED

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: Health Service Executive | Statement: [Health Act 2004, transfersFunctionsTo, Health Service Executive]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transfersFunctionsTo
Context triple: [Health Act 2004, transfersFunctionsTo, Health Service Executive]
  • A. transfersFunctionFrom
    Indicates that a function, role, or operational capability is moved or reassigned from one entity to another.
  • B. transferredFunctionsFrom
    Indicates that certain roles, duties, or responsibilities were moved from one entity to another.
  • C. allowsTransferOfFunctionsFrom
    Indicates that one entity grants permission or enables the shifting of responsibilities, duties, or operational functions from itself to another entity.
  • D. functionsTransferredUnder
    Indicates that certain responsibilities, duties, or operational roles have been moved from one entity to another.
  • E. transferredPromotionalFunctionsTo
    Indicates that one entity moved or reassigned its promotional responsibilities, duties, or activities to another entity.
  • F. None of above. chosen

Provenance (4 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_69f224ca2fa881908a3ac5fedf207b90 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe21b0cba48190b56c39e9f1c0eafa completed May 8, 2026, 5:47 p.m.
PD Predicate disambiguation batch_69fe204576848190aecf204e2adba5dc completed May 8, 2026, 5:41 p.m.
PDg Predicate description generation batch_69fe21afdc4c8190913ac4b55a9a5f52 completed May 8, 2026, 5:47 p.m.
Created at: April 29, 2026, 8:59 p.m.