Triple
T35754826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Columbia–Alberta border |
E1033412
|
entity |
| Predicate | hasNaturalBasis |
P199861
|
FINISHED |
| Object | orographic divide |
—
|
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: orographic divide | Statement: [British Columbia–Alberta border, hasNaturalBasis, orographic divide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNaturalBasis Context triple: [British Columbia–Alberta border, hasNaturalBasis, orographic divide]
-
A.
hasBasisIn
Indicates that one entity is founded, derived, or justified on the grounds of another entity.
-
B.
hasStandardBasis
Indicates that a given vector space is equipped with or possesses its usual canonical set of basis vectors.
-
C.
hasNaturalForm
Indicates that an entity possesses an inherent, unaltered, or naturally occurring form or state.
-
D.
hasBoardBasis
Indicates that one entity serves as the foundational basis or justification for the existence, composition, or decisions of a board associated with another entity.
-
E.
hasCanonicalBasis
Indicates that there exists a standard or preferred basis associated with an entity, typically used as the reference basis in its context.
- F. None of above. chosen
Provenance (4 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69ff5f5ddfcc819092563419f9e82d60 |
completed | May 9, 2026, 4:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.