Triple
T22921214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division No. 10, Alberta |
E568865
|
entity |
| Predicate | borderCityIncluded |
P15361
|
FINISHED |
| Object | Lloydminster |
—
|
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: Lloydminster | Statement: [Division No. 10, Alberta, borderCityIncluded, Lloydminster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCityIncluded Context triple: [Division No. 10, Alberta, borderCityIncluded, Lloydminster]
-
A.
hasBorderCity
chosen
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
B.
cityIsBorderCity
Indicates that a city is located on or near a boundary between two regions, countries, or administrative areas.
-
C.
borderCityOnUSSide
Indicates that a city is located on the U.S. side of an international border shared with another country.
-
D.
borderStreet
Indicates that a street forms or lies along the boundary between two geographic areas or properties.
-
E.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d5658c81908dbbb5882fcc1b8b |
completed | April 29, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:43 p.m.