Triple
T33862523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oak Lake, Manitoba, Canada |
E867959
|
entity |
| Predicate | recreationalFocus |
P112901
|
FINISHED |
| Object | lake-based tourism |
—
|
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: lake-based tourism | Statement: [Oak Lake, Manitoba, Canada, recreationalFocus, lake-based tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationalFocus Context triple: [Oak Lake, Manitoba, Canada, recreationalFocus, lake-based tourism]
-
A.
recreationalImportance
Indicates the degree to which something is valued or used for leisure, play, or recreational activities.
-
B.
hasRecreationalAspect
chosen
Indicates that something includes, involves, or is characterized by a recreational or leisure-related component or purpose.
-
C.
recreationLocation
Indicates the place where a recreational activity or leisure pursuit occurs.
-
D.
recreationRegion
Indicates that a location or area is designated or used as a region for recreational activities.
-
E.
hasRecreationalContext
Indicates that something occurs, is used, or is understood within a leisure, entertainment, or recreational setting or purpose.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009ebd0c8190b105fc1da649578b |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5a4f7881909324eb3c20ca96f1 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.