Triple

T13319005
Position Surface form Disambiguated ID Type / Status
Subject Derwent Innovation E317265 entity
Predicate supportsJurisdictionCoverage P4969 FINISHED
Object global 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: global | Statement: [Derwent Innovation, supportsJurisdictionCoverage, global]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsJurisdictionCoverage
Context triple: [Derwent Innovation, supportsJurisdictionCoverage, global]
  • A. supportsJurisdiction
    Indicates that one jurisdiction provides backing, authority, or legal support for the actions, decisions, or existence of another jurisdiction.
  • B. jurisdictionCovered chosen
    Indicates that a particular jurisdiction or legal authority is included within the scope or coverage of another entity, rule, or arrangement.
  • C. hasJurisidiction
    Indicates that one entity holds legal authority or control over another entity, area, or matter.
  • D. requiresCoveredJurisdictionsTo
    Indicates that one entity obligates another entity to include or address certain specified jurisdictions within its scope or activities.
  • E. providesCoverage
    Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
  • 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_69d806b4d62c81908d4ced1665414be5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99cfdc9388190af1fdd3cd4717bd8 completed April 11, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69d98f6babd88190a5d529df9584b9a4 completed April 11, 2026, 12:01 a.m.
Created at: April 9, 2026, 9:29 p.m.