Triple
T23109528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far North of Ontario |
E576275
|
entity |
| Predicate | hasPlanningProcess |
P72243
|
FINISHED |
| Object | community-based land use planning |
—
|
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: community-based land use planning | Statement: [Far North of Ontario, hasPlanningProcess, community-based land use planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningProcess Context triple: [Far North of Ontario, hasPlanningProcess, community-based land use planning]
-
A.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
B.
planningProcess
chosen
Indicates a relationship where an entity is engaged in or associated with the structured activity of defining goals, strategies, and steps to achieve a desired outcome.
-
C.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
D.
hasPlanningConcept
Indicates that an entity is associated with, defined by, or governed by a particular planning-related concept or framework.
-
E.
hasPlanningLevel
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e0d3d4881908e32837b3fbbb406 |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.