Triple
T29527214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaufort Inlet |
E749098
|
entity |
| Predicate | hasRecreationalImportance |
P168979
|
FINISHED |
| Object | sport fishing access point |
—
|
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: sport fishing access point | Statement: [Beaufort Inlet, hasRecreationalImportance, sport fishing access point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalImportance Context triple: [Beaufort Inlet, hasRecreationalImportance, sport fishing access point]
-
A.
recreationalImportance
chosen
Indicates the degree to which something is valued or used for leisure, play, or recreational activities.
-
B.
hasRecreationalAspect
Indicates that something includes, involves, or is characterized by a recreational or leisure-related component or purpose.
-
C.
isRecreationalResourceFor
Indicates that something serves as a facility, area, or service used by someone for leisure, recreation, or enjoyment.
-
D.
isRecreationalArea
Indicates that a place or space is designated and used primarily for leisure, relaxation, or recreational activities.
-
E.
hasRecreationPurpose
Indicates that something is used or intended to be used for recreational or leisure 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: April 28, 2026, 4:48 p.m.