Triple
T28949550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Vancouver from the North Shore |
E730969
|
entity |
| Predicate | separatingWaterBody |
P19305
|
FINISHED |
| Object | Burrard Inlet |
—
|
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: Burrard Inlet | Statement: [City of Vancouver from the North Shore, separatingWaterBody, Burrard Inlet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatingWaterBody Context triple: [City of Vancouver from the North Shore, separatingWaterBody, Burrard Inlet]
-
A.
separatedFromByWaterBody
chosen
Indicates that two entities are apart from each other with a body of water lying between them as the separating barrier.
-
B.
separatesLandmasses
Indicates that one entity (typically a physical feature like water or terrain) divides or creates a boundary between two or more landmasses.
-
C.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
D.
connectedBodyOfWater
Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
-
E.
riverSeparatingFrom
Indicates that one river branches off or diverges from another river, creating a separation between their flow paths.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 8:42 a.m.