Triple
T23033708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moose Cree First Nation |
E573536
|
entity |
| Predicate | hasTotalRegisteredPopulation |
P141158
|
FINISHED |
| Object | over 4000 |
—
|
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: over 4000 | Statement: [Moose Cree First Nation, hasTotalRegisteredPopulation, over 4000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTotalRegisteredPopulation Context triple: [Moose Cree First Nation, hasTotalRegisteredPopulation, over 4000]
-
A.
hasRegisteredPopulation
chosen
Indicates that an entity has an officially recorded number of inhabitants in a population registry or census.
-
B.
permanentPopulation
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
-
C.
hasResidentPopulation
Indicates that a place or administrative area has a population of people who live there permanently or for an extended period.
-
D.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
E.
governedPopulation
Indicates that one entity serves as the governing authority over the population of 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18482e78c8190a89681eec2edb812 |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:53 p.m.