Triple
T17083386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Albert, Saskatchewan |
E414530
|
entity |
| Predicate | nearbyLandCover |
P85343
|
FINISHED |
| Object | boreal forest |
—
|
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: boreal forest | Statement: [Prince Albert, Saskatchewan, nearbyLandCover, boreal forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyLandCover Context triple: [Prince Albert, Saskatchewan, nearbyLandCover, boreal forest]
-
A.
nearbyFeature
Indicates that one entity is located close to or in the immediate vicinity of another entity.
-
B.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
C.
hasNearbyLandscapeType
chosen
Indicates that one entity is located close to, or in the vicinity of, a particular type of landscape.
-
D.
nearestLandmass
Indicates that one landmass is the closest geographically to another specified point or landmass.
-
E.
hasNearbyPublicLand
Indicates that one entity is located close to an area of public land, such as parks, reserves, or other publicly accessible open spaces.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe4d3908190b23ce3c2d3fe7d14 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.