Triple
T16139299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Alberta |
E391609
|
entity |
| Predicate | dateProvinceCreated |
P73584
|
FINISHED |
| Object | 1905-09-01 |
—
|
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: 1905-09-01 | Statement: [Government of Alberta, dateProvinceCreated, 1905-09-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateProvinceCreated Context triple: [Government of Alberta, dateProvinceCreated, 1905-09-01]
-
A.
establishedAsProvinceIn
chosen
Indicates that an entity was formally designated or created as a province in a specified year or time period.
-
B.
stateTypeFounded
Indicates that a particular type or category of state was established or came into existence at a certain point or by a certain founding event.
-
C.
provinceAtTime
Indicates that an entity is a province of (or belongs to the jurisdiction of) another entity during a specified time or time interval.
-
D.
stateFoundedIn
Indicates that a particular state was established or came into existence in a specified year or time period.
-
E.
stateFounded
Indicates that a particular state was established or created at a specific time or by a specific founding event or agent.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a06e0988190b5cd62d422d058a2 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.