Triple
T28986760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boundary Road |
E734706
|
entity |
| Predicate | hasCityOnEastSide |
P175662
|
FINISHED |
| Object | Burnaby |
—
|
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 | Statement: [Boundary Road, hasCityOnEastSide, Burnaby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityOnEastSide Context triple: [Boundary Road, hasCityOnEastSide, Burnaby]
-
A.
hasFormerMunicipalityOnEastSide
Indicates that an entity previously functioned as a municipality located on the eastern side of another referenced entity.
-
B.
cityOnEastBank
Indicates that a city is located on the eastern bank of a river or similar dividing waterway.
-
C.
hasLanguageOnEasternSide
Indicates that a specified language is used or spoken on the eastern side of a given area, boundary, or region.
-
D.
regionalCenterOfEasternSide
Indicates that an entity functions as the primary administrative or functional center for the eastern part of a larger region or area.
-
E.
hasJurisdictionOnEast
Indicates that a governing authority or entity holds legal or administrative jurisdiction over an eastern area or region.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 28, 2026, 9:14 a.m.