Triple

T712289
Position Surface form Disambiguated ID Type / Status
Subject Oregon Administrative Rules E14235 entity
Predicate includesTypeOfProvision P11051 FINISHED
Object emergency rules 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: emergency rules | Statement: [Oregon Administrative Rules, includesTypeOfProvision, emergency rules]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesTypeOfProvision
Context triple: [Oregon Administrative Rules, includesTypeOfProvision, emergency rules]
  • A. includesRouteType
    Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
  • B. hasProvisionOn chosen
    Indicates that one entity contains, specifies, or includes a particular provision, clause, or stipulation concerning another entity or subject.
  • C. notableProvision
    Indicates that one entity is a significant or noteworthy clause, term, or condition contained within another entity, such as a document, agreement, or law.
  • D. protectionType
    Indicates the kind or method of protection that is applied to or associated with an entity.
  • E. isSubjectTo
    Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of 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_69a4934a36e081909e7abef98b898a4e completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a77fcc6881908a025bb21e44ad56 completed March 1, 2026, 8:54 p.m.
PD Predicate disambiguation batch_69a4a4f221b081909fbaa689fb20eb3e completed March 1, 2026, 8:43 p.m.
Created at: March 1, 2026, 7:36 p.m.