Triple
T33103694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saltery Bay |
E847126
|
entity |
| Predicate | distanceToPowellRiverByRoad_km |
P200572
|
FINISHED |
| Object | approximately 27 |
—
|
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: approximately 27 | Statement: [Saltery Bay, distanceToPowellRiverByRoad_km, approximately 27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToPowellRiverByRoad_km Context triple: [Saltery Bay, distanceToPowellRiverByRoad_km, approximately 27]
-
A.
distanceFromPowellRiver
chosen
Indicates the measured spatial distance between a given location and Powell River.
-
B.
distanceToVancouverByRoad
Indicates the length of the route required to travel by road from a given place to Vancouver.
-
C.
distanceFromVictoria
Indicates the measured distance between a given entity or location and Victoria.
-
D.
distanceToRevelstoke
Indicates the spatial distance between a given entity’s location and the location of Revelstoke.
-
E.
distanceToVictoriaByRoad_km
Indicates the distance in kilometers between two places when traveling by road to Victoria.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:26 a.m.