Triple
T24940780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Membertou First Nation |
E623445
|
entity |
| Predicate | hasOnReservePopulationStatus |
P141159
|
FINISHED |
| Object | urbanized |
—
|
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: urbanized | Statement: [Membertou First Nation, hasOnReservePopulationStatus, urbanized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnReservePopulationStatus Context triple: [Membertou First Nation, hasOnReservePopulationStatus, urbanized]
-
A.
hasOnReservePopulation
chosen
Indicates that a population of the entity is set aside or maintained in reserve, rather than being part of the main active population.
-
B.
hasOffReservePopulation
Indicates that a group or community has members of its population living outside a designated reserve area.
-
C.
isOnReserve
Indicates that an entity is currently set aside or held in reserve, rather than being in regular or active use.
-
D.
hasPopulationStatus
Indicates the current demographic condition or classification of a population associated with an entity.
-
E.
hasReserveStatus
Indicates that an entity holds a designated reserve or backup status in relation to another entity or role.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 5:30 a.m.