Triple
T37815825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Bar area along the Fraser River |
E942770
|
entity |
| Predicate | isRelativelyNear |
P45695
|
FINISHED |
| Object | Fraser Canyon communities |
—
|
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: Fraser Canyon communities | Statement: [High Bar area along the Fraser River, isRelativelyNear, Fraser Canyon communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelativelyNear Context triple: [High Bar area along the Fraser River, isRelativelyNear, Fraser Canyon communities]
-
A.
isCloseTo
chosen
Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
-
B.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
-
C.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
D.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
E.
closerTo
Indicates that one entity is at a smaller distance to a reference entity than another entity is.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.