Triple

T25602489
Position Surface form Disambiguated ID Type / Status
Subject Presinge E641823 entity
Predicate appliesMunicipalRegulations P16838 FINISHED
Object Presinge municipal 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: Presinge municipal regulations | Statement: [Presinge, appliesMunicipalRegulations, Presinge municipal regulations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesMunicipalRegulations
Context triple: [Presinge, appliesMunicipalRegulations, Presinge municipal regulations]
  • A. hasLocalOrdinances chosen
    Indicates that a governing body or jurisdiction has established and enacted specific local ordinances or regulations.
  • B. municipalityAgreementRequired
    Indicates that a formal agreement or approval from the relevant municipality is required for the associated action or relationship to proceed.
  • C. cityRegulationImpact
    Indicates how a specific city regulation affects or influences certain activities, entities, or conditions.
  • D. hasMunicipalStatute
    Indicates that a municipality is governed or regulated by a specific municipal statute or ordinance.
  • E. hasRegulations
    Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation 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_69e75dc6ccf081908d49578fd36a76d5 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f6691f5e188190b12c7b2eb729a45e completed May 2, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69f66598d6008190a7ca8ff80399fd34 completed May 2, 2026, 8:59 p.m.
Created at: April 21, 2026, 4:36 p.m.