Triple

T10178660
Position Surface form Disambiguated ID Type / Status
Subject Frontier Crimes Regulations E235924 entity
Predicate limitsRight P40382 FINISHED
Object access to regular courts 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: access to regular courts | Statement: [Frontier Crimes Regulations, limitsRight, access to regular courts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: limitsRight
Context triple: [Frontier Crimes Regulations, limitsRight, access to regular courts]
  • A. restrictedRight chosen
    Indicates that an entity’s ability to exercise a particular right is limited, constrained, or subject to specific conditions or prohibitions.
  • B. limitaCon
    Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
  • C. coversRight
    Indicates that one entity extends over, protects, or conceals the right side of another entity.
  • D. leftPosition
    Indicates that one entity is located to the left side of another entity in space or ordering.
  • E. limitsPriorityOf
    Indicates that one entity imposes a maximum allowable priority level on another entity’s priority.
  • 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_69ca84d1d5f88190ab878a1021ecff68 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdecd620808190892c6e3074500280 completed April 2, 2026, 4:13 a.m.
PD Predicate disambiguation batch_69cd7c79f21c8190a7f31b2eab80b8ba completed April 1, 2026, 8:13 p.m.
Created at: March 30, 2026, 9:11 p.m.