Triple
T35421436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Columbia–Northwest Territories border |
E1023804
|
entity |
| Predicate | hasNeighboringBorder |
P37800
|
FINISHED |
| Object | British Columbia–Yukon border |
—
|
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: British Columbia–Yukon border | Statement: [British Columbia–Northwest Territories border, hasNeighboringBorder, British Columbia–Yukon border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringBorder Context triple: [British Columbia–Northwest Territories border, hasNeighboringBorder, British Columbia–Yukon border]
-
A.
hasNeighboringFeature
Indicates that one feature is located adjacent to or directly next to another feature in space.
-
B.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
C.
hasBorderElement
Indicates that one entity includes or is associated with another entity that forms part of its boundary or edge.
-
D.
hasBorderRelation
chosen
Indicates that one entity shares a boundary or border with another entity.
-
E.
hasBorderDirection
Indicates that one entity’s border lies in, or is oriented toward, a specified cardinal or relative direction with respect to another entity.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
Created at: May 3, 2026, 4:03 p.m.