Triple

T32518529
Position Surface form Disambiguated ID Type / Status
Subject Nominet UK E831120 entity
Predicate usesDisputePolicy P125340 FINISHED
Object Nominet Dispute Resolution Service (DRS) 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: Nominet Dispute Resolution Service (DRS) | Statement: [Nominet UK, usesDisputePolicy, Nominet Dispute Resolution Service (DRS)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesDisputePolicy
Context triple: [Nominet UK, usesDisputePolicy, Nominet Dispute Resolution Service (DRS)]
  • A. disputePolicy
    Indicates that there is a formal disagreement or conflict regarding a policy, typically triggering procedures for review, negotiation, or resolution.
  • B. hasDisputeRegime chosen
    Indicates that there exists a specific dispute-handling framework, system, or set of rules governing how disputes related to the subject are managed or resolved.
  • C. hasDisputeWith
    Indicates that there is a conflict, disagreement, or contested issue between two entities.
  • D. hasDisputeType
    Indicates that an entity is associated with a particular category or type of dispute.
  • E. hasDisputedClause
    Indicates that a particular clause within an agreement or document is subject to disagreement, challenge, or contention between involved parties.
  • 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_69f34923e1548190be0524205d8cdf8f completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6f8164698819090c1b471f1caa4c6 completed May 3, 2026, 7:24 a.m.
PD Predicate disambiguation batch_69f6f6619404819084662aef1238261c completed May 3, 2026, 7:16 a.m.
Created at: May 1, 2026, 1 a.m.