Triple

T8001318
Position Surface form Disambiguated ID Type / Status
Subject Court of Protection E186253 entity
Predicate canAlsoApplyTo P70805 FINISHED
Object young people aged 16 and 17 who lack capacity 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: young people aged 16 and 17 who lack capacity | Statement: [Court of Protection, canAlsoApplyTo, young people aged 16 and 17 who lack capacity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canAlsoApplyTo
Context triple: [Court of Protection, canAlsoApplyTo, young people aged 16 and 17 who lack capacity]
  • A. appliesAlsoTo chosen
    Indicates that a condition, rule, or characteristic that applies to one entity is additionally applicable to another entity.
  • B. appliesTo
    Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
  • C. canAlsoBe
    Indicates that something has an additional possible state, role, or classification beyond its primary one.
  • D. appliesFrom
    Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
  • E. canAlsoIndicate
    Indicates that something may additionally signify, represent, or serve as another meaning or function beyond its primary one.
  • 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_69ca82aaaf24819084b94d18f699ba53 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3c9cd06081908b62bb41e228c321 completed March 31, 2026, 3:16 a.m.
PD Predicate disambiguation batch_69cb0483d3b48190b250c7603d747bca completed March 30, 2026, 11:17 p.m.
Created at: March 30, 2026, 5:18 p.m.