Triple
T25594425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milton |
E641608
|
entity |
| Predicate | usesCensusDataFrom |
P157774
|
FINISHED |
| Object | Statistics Canada |
—
|
NE NERFINISHED |
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: Statistics Canada | Statement: [Milton, usesCensusDataFrom, Statistics Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCensusDataFrom Context triple: [Milton, usesCensusDataFrom, Statistics Canada]
-
A.
censusUsage
chosen
Indicates that an entity makes use of census data or statistics for its activities, analysis, or decision-making.
-
B.
census
Indicates that an official count or survey is conducted to determine the number and characteristics of a population within a defined area or group.
-
C.
basedOnCensusYear
Indicates that something (such as data, a decision, or a classification) is derived from or determined using information from a specific census year.
-
D.
censusReference
Indicates that one entity serves as a reference or identifier for another entity within a census or population-record context.
-
E.
hasCensusAreas
Indicates that an entity is associated with one or more defined census areas used for demographic or statistical purposes.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 4:26 p.m.