Triple
T36506396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hastings Street |
E899476
|
entity |
| Predicate | formsCommercialHeartOf |
P193630
|
FINISHED |
| Object | Burnaby Heights |
—
|
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: Burnaby Heights | Statement: [Hastings Street, formsCommercialHeartOf, Burnaby Heights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsCommercialHeartOf Context triple: [Hastings Street, formsCommercialHeartOf, Burnaby Heights]
-
A.
commercialForm
Indicates the commercial or marketed form in which something (such as a product, substance, or medicine) is offered or sold.
-
B.
commercialAccess
Indicates that an entity is permitted to use or access something for commercial or profit-generating purposes.
-
C.
commercialFundingSource
Indicates that the entity receives financial support or backing from a commercial (for-profit) organization or source.
-
D.
businessForm
Indicates the legal or organizational structure under which a business operates (e.g., sole proprietorship, partnership, corporation).
-
E.
commercialSuccessIn
Indicates that something has achieved notable commercial success within a specified market, region, or domain.
- F. None of above. chosen
Provenance (4 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
| PDg | Predicate description generation | batch_69fd4d16dd20819096957c40f43cd971 |
completed | May 8, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:10 p.m.