Triple
T26431471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quetico–Superior region |
E664519
|
entity |
| Predicate | recreationAccessMode |
P6529
|
FINISHED |
| Object | non-motorized travel |
—
|
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: non-motorized travel | Statement: [Quetico–Superior region, recreationAccessMode, non-motorized travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationAccessMode Context triple: [Quetico–Superior region, recreationAccessMode, non-motorized travel]
-
A.
recreationAccess
Indicates that one entity provides or has the ability to use recreational facilities, activities, or spaces associated with another entity.
-
B.
recreationAccessPoint
Indicates a location or facility that serves as an entry or starting point for engaging in recreational activities.
-
C.
accessMode
chosen
Indicates the manner or method by which an entity can be accessed, used, or interacted with.
-
D.
recreationSetting
Indicates the type of environment or context in which a recreational activity takes place.
-
E.
recreationUseLevel
Indicates the intensity or degree to which an entity is used for recreational activities.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 11:49 p.m.