Triple

T27663175
Position Surface form Disambiguated ID Type / Status
Subject CAA E697169 entity
Predicate cannotRestrict P166186 FINISHED
Object which specific end-entities receive certificates 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: which specific end-entities receive certificates | Statement: [CAA, cannotRestrict, which specific end-entities receive certificates]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cannotRestrict
Context triple: [CAA, cannotRestrict, which specific end-entities receive certificates]
  • A. notRestrictedBy
    Indicates that something is free from limitations, constraints, or prohibitions imposed by another entity or condition.
  • B. cannotVeto
    Indicates that an entity lacks the authority or ability to reject, block, or override a decision, proposal, or action made by another entity.
  • C. cannotGrant
    Indicates that an entity lacks the authority, permission, or ability to confer a requested right, access, or resource to another entity.
  • D. mayRestrictActivity
    Indicates that one entity has the authority or ability to limit, constrain, or prohibit certain actions or behaviors of another entity.
  • E. cannotShow
    Indicates that one entity is unable or not permitted to display, reveal, or present another entity.
  • F. None of above. chosen

Provenance (4 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_69ef590b85a4819083ec7c12bd3c9c10 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f66003a3f48190a2ba6da5aafbb5cb completed May 2, 2026, 8:35 p.m.
PD Predicate disambiguation batch_69f65c2198208190a3954086c22cfcbf completed May 2, 2026, 8:18 p.m.
PDg Predicate description generation batch_69f65f75ac608190a62cd6afce14f68e completed May 2, 2026, 8:32 p.m.
Created at: April 27, 2026, 2:37 p.m.