Triple
T35372577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukon–British Columbia border |
E1021814
|
entity |
| Predicate | cameIntoUseAsYukonBoundary |
P183275
|
FINISHED |
| Object | 1898 |
—
|
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: 1898 | Statement: [Yukon–British Columbia border, cameIntoUseAsYukonBoundary, 1898]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameIntoUseAsYukonBoundary Context triple: [Yukon–British Columbia border, cameIntoUseAsYukonBoundary, 1898]
-
A.
westernBoundaryReference
Indicates the reference feature or limit that defines the western boundary of an entity or area.
-
B.
northernBoundaryExtendedTo
Indicates that the northern boundary of one entity has been lengthened or expanded to reach or include another specified reference point or area.
-
C.
westernTerminusAtBorderWith
Indicates that something’s western endpoint or final location lies at a border shared with another region or entity.
-
D.
northTerminusRegion
Indicates that a specified region serves as the northern endpoint or terminus of a linear feature, route, or entity.
-
E.
wasFrontierBetween
Indicates that one entity historically served as the boundary or border region separating two other entities.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:03 p.m.