Triple

T3210032
Position Surface form Disambiguated ID Type / Status
Subject Illinois Medical District E67255 entity
Predicate zoningStatus P727 FINISHED
Object special-use district 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: special-use district | Statement: [Illinois Medical District, zoningStatus, special-use district]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: zoningStatus
Context triple: [Illinois Medical District, zoningStatus, special-use district]
  • A. zoningCharacter chosen
    Indicates how the regulatory or functional nature of a geographic area is defined or classified in terms of land-use zoning.
  • B. territorialStatus
    Indicates the legal or political condition of control, sovereignty, or jurisdiction that applies to a specific territory.
  • C. governingStatus
    Indicates the political or administrative condition under which an entity is currently governed or exercising governing authority.
  • D. hasLandStatus
    Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
  • E. roofStatus
    Indicates the current condition or state of a roof, such as whether it is intact, damaged, under repair, or replaced.
  • 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_69ad858ac36c81909962589cd277d6e2 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adaab701c48190b91404ab416f7ce3 completed March 8, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69ad9e09b83881908801d79c3d9254f9 completed March 8, 2026, 4:04 p.m.
Created at: March 8, 2026, 3:07 p.m.