Triple

T1613748
Position Surface form Disambiguated ID Type / Status
Subject Chicago Municipal Code E34665 entity
Predicate requiresComplianceFrom P100 FINISHED
Object residents of Chicago 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: residents of Chicago | Statement: [Chicago Municipal Code, requiresComplianceFrom, residents of Chicago]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresComplianceFrom
Context triple: [Chicago Municipal Code, requiresComplianceFrom, residents of Chicago]
  • A. requiresComplianceTestingBy
    Indicates that one entity must undergo compliance testing conducted or overseen by another entity.
  • B. requiredBy
    Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
  • C. regulatesComplianceWith
    Indicates that one entity oversees, enforces, or sets rules to ensure another entity adheres to specified standards, laws, or requirements.
  • D. requiresSanctioningBody
    Indicates that an action, event, or decision must be approved or authorized by a designated sanctioning authority or governing body.
  • E. requires chosen
    Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
  • 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_69a885ffc5ec819091afa325d5f9611c completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a93fef600c819080fe75c42c8e6dac completed March 5, 2026, 8:33 a.m.
PD Predicate disambiguation batch_69a907c52a548190b648a31ea306dd5b completed March 5, 2026, 4:34 a.m.
Created at: March 4, 2026, 7:28 p.m.