Triple
T23840665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S0N |
E590976
|
entity |
| Predicate | primaryCommunityProvince |
P32556
|
FINISHED |
| Object | Saskatchewan |
—
|
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: Saskatchewan | Statement: [S0N, primaryCommunityProvince, Saskatchewan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCommunityProvince Context triple: [S0N, primaryCommunityProvince, Saskatchewan]
-
A.
provinceWithCommunity
chosen
Indicates that a given province contains, includes, or is associated with a particular community.
-
B.
governingProvince
Indicates that one administrative unit or authority has official governing control over a specified province.
-
C.
exportProvince
Indicates the province from which goods, services, or resources are exported.
-
D.
baseProvince
Indicates that one administrative or territorial unit serves as the primary or originating province associated with another entity.
-
E.
traditionalProvince
Indicates that an entity is located in, associated with, or belongs to a historically recognized or customary provincial region rather than a modern administrative unit.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c88797d4819081831fd3f8822ef4 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:08 p.m.