Triple
T22728325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alberta census divisions |
E562056
|
entity |
| Predicate | hasLevelCode |
P104687
|
FINISHED |
| Object | CD |
—
|
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: CD | Statement: [Alberta census divisions, hasLevelCode, CD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelCode Context triple: [Alberta census divisions, hasLevelCode, CD]
-
A.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
B.
hasISOCodeLevel
chosen
Indicates that an entity is associated with a specific level or tier within an ISO (International Organization for Standardization) coding system.
-
C.
hasLevelType
Indicates that an entity is associated with a specific type or category of level (e.g., difficulty, hierarchy, or stage).
-
D.
hasLevelNumber
Indicates that an entity is associated with a specific level identified by a numerical value.
-
E.
hasCategoryLevel
Indicates that something is associated with a specific hierarchical category or tier within a classification system.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792b22cc819099aa00bb2dbacce3 |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:21 p.m.