Triple

T599374
Position Surface form Disambiguated ID Type / Status
Subject City of Falls Church E11458 entity
Predicate hasLocalOrdinances P16838 FINISHED
Object zoning 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: zoning regulations | Statement: [City of Falls Church, hasLocalOrdinances, zoning regulations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocalOrdinances
Context triple: [City of Falls Church, hasLocalOrdinances, zoning regulations]
  • A. foundOrdinances
    Indicates that one entity has discovered, identified, or come across specific ordinances (such as laws, regulations, or decrees) associated with another entity or context.
  • B. recognizedAsOrdinanceBy
    Indicates that something is formally acknowledged or accepted as an ordinance by a particular authority or governing body.
  • C. hasLocalGovernmentBody
    Indicates that an entity is administered or overseen by a specific local government authority or governing body.
  • D. hasMunicipalGovernment
    Indicates that an entity is administered or governed by a municipal-level governmental authority.
  • E. hasMunicipalSections
    Indicates that a municipality is divided into and associated with specific internal administrative sections or districts.
  • F. None of above. chosen

Provenance (4 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_69a4932779b881908688590d59c71900 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49dc4f7d08190990f70b9b3af6ce5 completed March 1, 2026, 8:12 p.m.
PD Predicate disambiguation batch_69a49cf59cd0819084e67981cb371e25 completed March 1, 2026, 8:09 p.m.
PDg Predicate description generation batch_69a49dc0e6a08190b81d82a6f2571c41 completed March 1, 2026, 8:12 p.m.
Created at: March 1, 2026, 7:35 p.m.