Triple

T21362212
Position Surface form Disambiguated ID Type / Status
Subject Montrose Avenue E526810 entity
Predicate hasApproximateAddressRange P20336 FINISHED
Object 4400 North in Chicago grid 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: 4400 North in Chicago grid | Statement: [Montrose Avenue, hasApproximateAddressRange, 4400 North in Chicago grid]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateAddressRange
Context triple: [Montrose Avenue, hasApproximateAddressRange, 4400 North in Chicago grid]
  • A. hasApproximateLocation
    Indicates that an entity is associated with a location that is known only imprecisely or within a general area rather than an exact position.
  • B. hasApproximateCoordinates
    Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
  • C. hasApproximateExtent chosen
    Indicates that one entity has a spatial, temporal, or quantitative extent that is only roughly or approximately specified rather than exact.
  • D. hasAddress
    Indicates that an entity is associated with a specific address or location.
  • E. hasApproximateOrigin
    Indicates that an entity originates from a source or location that is known only approximately rather than precisely.
  • 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_69e0b51d8a308190b09113b3b3f9bc15 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b06b219c81908f7674ae459e7931 completed April 22, 2026, 11:26 a.m.
PD Predicate disambiguation batch_69e6162bbfc88190a3e75859941b2638 completed April 20, 2026, 12:03 p.m.
Created at: April 16, 2026, 5:08 p.m.