Triple

T31056379
Position Surface form Disambiguated ID Type / Status
Subject Child Safety Order E791408 entity
Predicate sanctionForBreach P66185 FINISHED
Object possible care proceedings 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: possible care proceedings | Statement: [Child Safety Order, sanctionForBreach, possible care proceedings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sanctionForBreach
Context triple: [Child Safety Order, sanctionForBreach, possible care proceedings]
  • A. sanction
    Indicates the imposition of an official penalty or restrictive measure by an authority in response to certain actions or behaviors.
  • B. breachedDuring
    Indicates that one entity violated, broke, or failed to uphold another entity (such as a rule, contract, or security measure) within a specified time period or event.
  • C. coSanctionedBy
    Indicates that an action, decision, or measure is jointly authorized, approved, or endorsed by multiple entities.
  • D. sanctioningRules chosen
    Indicates the rules or conditions under which sanctions or penalties are imposed in response to certain actions or behaviors.
  • E. sanctioningLevel
    Indicates the degree or severity of formal penalties, restrictions, or disciplinary measures imposed in response to a violation or noncompliant behavior.
  • 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_69f224cb08908190ba71ad9aa87518ed completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69dfdda708190be290c7bec205445 completed May 3, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69f69d1a37e081908d1d86b90ff502bd completed May 3, 2026, 12:55 a.m.
Created at: April 29, 2026, 9 p.m.