Triple

T178860
Position Surface form Disambiguated ID Type / Status
Subject Capitol Visitor Center security checkpoints E3638 entity
Predicate hasRegulation P2846 FINISHED
Object restrictions on weapons 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: restrictions on weapons | Statement: [Capitol Visitor Center security checkpoints, hasRegulation, restrictions on weapons]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegulation
Context triple: [Capitol Visitor Center security checkpoints, hasRegulation, restrictions on weapons]
  • A. regulatesUse
    Indicates that one entity controls, governs, or sets rules for how another entity may be used.
  • B. requiresDomesticLegislation
    Indicates that the fulfillment, implementation, or enforcement of one entity depends on the adoption or existence of specific domestic legislation by another entity (typically a state or jurisdiction).
  • C. regulatoryDomain
    Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
  • D. hasRule chosen
    Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
  • E. hasDietaryLaw
    Indicates that one entity prescribes, follows, or is governed by a specific set of dietary rules or restrictions associated with another entity.
  • 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_69a25374990081909766d30c79a18e0e completed Feb. 28, 2026, 2:31 a.m.
NER Named-entity recognition batch_69a25900709c8190a65e778936be5dd5 completed Feb. 28, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69a2566b53d481909c0ed40dd3719e8c completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:39 a.m.