Triple
T8882638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kapuskasing |
E211446
|
entity |
| Predicate | hasCensusRole |
P53267
|
FINISHED |
| Object | population centre |
—
|
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: population centre | Statement: [Kapuskasing, hasCensusRole, population centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCensusRole Context triple: [Kapuskasing, hasCensusRole, population centre]
-
A.
hasLocalGovernanceRole
Indicates that an entity holds an official position or responsibility within a local or municipal governing body.
-
B.
hasRegionalRole
Indicates that an entity holds a specific role, function, or responsibility within a defined geographic region.
-
C.
hasStatisticalRole
Indicates that an entity participates in a context (such as a study, dataset, or analysis) with a specific statistical function or role (e.g., variable, parameter, estimator).
-
D.
includedInCensus
chosen
Indicates that an entity was recorded or counted as part of a specific census.
-
E.
hasCivicFunction
Indicates that an entity performs, is responsible for, or is associated with an official public or civic role, duty, or service.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc616a01f48190b8bbde0e898a38c7 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.