Triple
T6108180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lloydminster cross-border area |
E136166
|
entity |
| Predicate | legalStatusInAlberta |
P2250
|
FINISHED |
| Object | city in 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: city in Alberta | Statement: [Lloydminster cross-border area, legalStatusInAlberta, city in Alberta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInAlberta Context triple: [Lloydminster cross-border area, legalStatusInAlberta, city in Alberta]
-
A.
usedLegalStatus
Indicates that one entity applies or relies on the legal status or classification of another entity in a given context.
-
B.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
C.
hasLegalStatus
chosen
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
D.
legalStatusVariesBy
Indicates that the legal status of something differs depending on a specified jurisdiction, context, or set of conditions.
-
E.
legalStatusModern
Indicates the current legal standing or classification of an entity under contemporary law or regulatory frameworks.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b81fad081909b622cafc6d51249 |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.