Triple

T1609169
Position Surface form Disambiguated ID Type / Status
Subject Revenue, Reporting, and Compliance Management E34576 entity
Predicate usesRegulation P12290 FINISHED
Object federal natural resource revenue regulations 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: federal natural resource revenue regulations | Statement: [Revenue, Reporting, and Compliance Management, usesRegulation, federal natural resource revenue regulations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesRegulation
Context triple: [Revenue, Reporting, and Compliance Management, usesRegulation, federal natural resource revenue regulations]
  • A. supportsRegulation
    Indicates that one entity endorses, backs, or advocates for the implementation or continuation of a specific regulation.
  • B. regulatesUse
    Indicates that one entity controls, governs, or sets rules for how another entity may be used.
  • C. worksOnRegulationType chosen
    Indicates that an entity is involved in work or activities related to a specific type or category of regulation.
  • D. regulationStatus
    Indicates the regulatory condition or compliance state that applies to an entity under relevant rules or laws.
  • E. regulatesComplianceWith
    Indicates that one entity oversees, enforces, or sets rules to ensure another entity adheres to specified standards, laws, or requirements.
  • 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_69a885fea6a481909fe83ba6441f1774 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a93fa6926081908bc78d15c0be3185 completed March 5, 2026, 8:32 a.m.
PD Predicate disambiguation batch_69a907c35f848190a2428c52e81d013e completed March 5, 2026, 4:34 a.m.
Created at: March 4, 2026, 7:28 p.m.