Triple

T37877472
Position Surface form Disambiguated ID Type / Status
Subject Proposition 2½ property tax limits E944771 entity
Predicate allowsExceptionVia P68180 FINISHED
Object override 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: override | Statement: [Proposition 2½ property tax limits, allowsExceptionVia, override]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allowsExceptionVia
Context triple: [Proposition 2½ property tax limits, allowsExceptionVia, override]
  • A. allowedReturn
    Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
  • B. providesExemptionsTo chosen
    Indicates that one entity grants or offers exemptions, waivers, or exceptions from rules, obligations, or requirements to another entity.
  • C. includesException
    Indicates that one entity explicitly contains, references, or accounts for a specified exception within its definition, behavior, or processing.
  • D. allows
    Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
  • E. supportsExceptionProcessing
    Indicates that one entity provides the capability or mechanism for another entity to handle or process exceptions.
  • 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_69f76eef55d481908ca6660b4b532550 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fd68abf52881909c5a390c362b7c59 completed May 8, 2026, 4:38 a.m.
PD Predicate disambiguation batch_69fd6812d0c88190930d8fa2d4b92490 completed May 8, 2026, 4:35 a.m.
Created at: May 3, 2026, 4:19 p.m.