Triple

T25237810
Position Surface form Disambiguated ID Type / Status
Subject Race Relations Act 1965 E632384 entity
Predicate limitedScope P30064 FINISHED
Object did not cover employment 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: did not cover employment | Statement: [Race Relations Act 1965, limitedScope, did not cover employment]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: limitedScope
Context triple: [Race Relations Act 1965, limitedScope, did not cover employment]
  • A. limitedPracticeOf
    Indicates that one entity engages in or allows only a restricted or reduced extent of a particular practice, activity, or method in relation to another entity.
  • B. reductionOfScope chosen
    Indicates a relationship where the extent, coverage, or range of something is decreased or limited compared to its previous or potential scope.
  • C. limitedIssueOf
    Indicates that one entity is issued or made available in a restricted or finite quantity by another entity.
  • D. scopeOfUse
    Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
  • E. oftenRestrictedTo
    Indicates that the use, occurrence, or applicability of something is frequently limited to a particular subset, context, or condition.
  • 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_69e75a8ec5f88190b9eba06ae42b413a completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f47dfc523c8190b61295b451d1e5cd completed May 1, 2026, 10:18 a.m.
PD Predicate disambiguation batch_69f44d849e7c81909945438f40e35362 completed May 1, 2026, 6:51 a.m.
Created at: April 21, 2026, 1:07 p.m.