Triple
T32270150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christie Street and Bloor Street West, Toronto |
E824392
|
entity |
| Predicate | hasNearbyResidentialBuildingType |
P122880
|
FINISHED |
| Object | low-rise apartments |
—
|
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: low-rise apartments | Statement: [Christie Street and Bloor Street West, Toronto, hasNearbyResidentialBuildingType, low-rise apartments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyResidentialBuildingType Context triple: [Christie Street and Bloor Street West, Toronto, hasNearbyResidentialBuildingType, low-rise apartments]
-
A.
hasNearbyPropertyType
Indicates that one entity has another entity of a specified property type located in close physical proximity to it.
-
B.
hasResidentialBuildingsType
chosen
Indicates that an entity is associated with a specific type or category of residential buildings.
-
C.
hasNeighboringBuilding
Indicates that one building is located adjacent to or directly next to another building.
-
D.
hasResidentialBuilding
Indicates that an entity possesses, contains, or is associated with a residential building as part of its properties or components.
-
E.
hasNearbyInfrastructureType
Indicates that an entity is located close to infrastructure of a specified type.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 1, 2026, 12:42 a.m.