Triple
T38188748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vancouver–Kelowna |
E1005392
|
entity |
| Predicate | startPointWaterbody |
P180297
|
FINISHED |
| Object | Strait of Georgia vicinity |
—
|
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: Strait of Georgia vicinity | Statement: [Vancouver–Kelowna, startPointWaterbody, Strait of Georgia vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startPointWaterbody Context triple: [Vancouver–Kelowna, startPointWaterbody, Strait of Georgia vicinity]
-
A.
startPointOfWaterway
chosen
Indicates that a location or feature serves as the starting point or origin of a waterway.
-
B.
startBodyOfWater
Indicates that a body of water begins or originates at the referenced location or entity.
-
C.
navigatesWaterBody
Indicates that an entity moves through or across a body of water as a means of travel or operation.
-
D.
addressesWaterBody
Indicates that an action, plan, or measure is directed toward managing, affecting, or dealing with a specific water body.
-
E.
locatedOnWaterbody
Indicates that an entity is situated on or directly adjacent to a specified body of water.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0164b052608190adc93240dad50a06 |
completed | May 11, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_6a01637fd3ac8190970eb09650d1e659 |
completed | May 11, 2026, 5:05 a.m. |
Created at: May 3, 2026, 4:29 p.m.