Triple
T16274519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alberta Act, 1905 |
E395088
|
entity |
| Predicate | regionCreated |
P115300
|
FINISHED |
| Object | Prairie province of Alberta |
—
|
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: Prairie province of Alberta | Statement: [Alberta Act, 1905, regionCreated, Prairie province of Alberta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCreated Context triple: [Alberta Act, 1905, regionCreated, Prairie province of Alberta]
-
A.
regionNameCreated
Indicates that a specific region was created with the given name.
-
B.
regionalUnitCreatedIn
chosen
Indicates that a regional administrative unit was established or officially created in a specified time or event.
-
C.
regionNumberCreated
Indicates that a specific numbered region was created or established as a distinct area.
-
D.
regionRecord
Indicates that a record or entry is associated with, belongs to, or is stored for a particular geographic or administrative region.
-
E.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2460c2d948190813b66e539a64a70 |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.