Triple
T27682559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lloydminster |
E697944
|
entity |
| Predicate | provinceLevelLegislationAlberta |
P125511
|
FINISHED |
| Object | Lloydminster Charter (Alberta) |
—
|
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 Charter (Alberta) | Statement: [Lloydminster, provinceLevelLegislationAlberta, Lloydminster Charter (Alberta)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceLevelLegislationAlberta Context triple: [Lloydminster, provinceLevelLegislationAlberta, Lloydminster Charter (Alberta)]
-
A.
inCanadianProvince
Indicates that one entity is located within, or is a part of, a specified Canadian province.
-
B.
usedInCanadianProvince
Indicates that something is utilized, applied, or in operation within the jurisdiction of a Canadian province.
-
C.
governingProvince
Indicates that one administrative unit or authority has official governing control over a specified province.
-
D.
protectedProvince
Indicates that a province is under protection or safeguarding by another entity or authority.
-
E.
legalStatusCanada
chosen
Indicates the legal classification or standing of an entity under Canadian law.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 27, 2026, 2:47 p.m.