Triple
T28546968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York, Ontario |
E722468
|
entity |
| Predicate | notableNeighbourhood |
P98915
|
FINISHED |
| Object | Weston |
—
|
NE NERFINISHED |
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: Weston | Statement: [York, Ontario, notableNeighbourhood, Weston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNeighbourhood Context triple: [York, Ontario, notableNeighbourhood, Weston]
-
A.
notableNeighborhoodType
Indicates that a neighborhood is notably characterized by, or strongly associated with, a particular type or category (e.g., residential, commercial, historic).
-
B.
notableUrbanEnclave
chosen
Indicates that an entity is recognized as a distinct, significant urban area or neighborhood within a larger city or metropolitan region.
-
C.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
D.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
E.
typicalNeighborhoods
Indicates that the associated neighborhoods are characteristic or commonly found examples for the given entity or context.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a01302a80ec8190a27692f09ac38a80 |
completed | May 11, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_6a012fad62308190a53f8b4a071eb245 |
completed | May 11, 2026, 1:23 a.m. |
Created at: April 28, 2026, 3:39 a.m.