Triple

T336197
Position Surface form Disambiguated ID Type / Status
Subject Religious Land Use and Institutionalized Persons Act E6731 entity
Predicate appliesInContext P1129 FINISHED
Object land use decisions 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: land use decisions | Statement: [Religious Land Use and Institutionalized Persons Act, appliesInContext, land use decisions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesInContext
Context triple: [Religious Land Use and Institutionalized Persons Act, appliesInContext, land use decisions]
  • A. appliesAt
    Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
  • B. appliesTo chosen
    Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
  • C. appliesAcross
    Indicates that a condition, rule, or property holds uniformly over multiple items, cases, or contexts.
  • D. appliesToPosition
    Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific position or role.
  • E. appliesFramework
    Indicates that one entity uses or implements a particular framework in relation to another entity or context.
  • 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_69a2e79434908190a9d5afe415153ad9 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eac950388190829875a07d821ddf completed Feb. 28, 2026, 1:16 p.m.
PD Predicate disambiguation batch_69a2e94f049881908f10bb6548a8bb2e completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.