Triple
T18468556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maupin, Oregon |
E451229
|
entity |
| Predicate | hasOutdoorIndustry |
P41520
|
FINISHED |
| Object | rafting outfitters |
—
|
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: rafting outfitters | Statement: [Maupin, Oregon, hasOutdoorIndustry, rafting outfitters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorIndustry Context triple: [Maupin, Oregon, hasOutdoorIndustry, rafting outfitters]
-
A.
hasOutdoorReputation
Indicates that an entity is known or regarded for qualities, activities, or status specifically related to the outdoors.
-
B.
hasOutdoorEducation
Indicates that an entity provides, includes, or is associated with educational activities or programs conducted in outdoor or natural environments.
-
C.
isOutdoor
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
-
D.
hasOutdoorFocus
chosen
Indicates a relationship where an entity is primarily concerned with, oriented toward, or specialized in outdoor environments, activities, or contexts.
-
E.
hasOutdoorResource
Indicates that an entity is associated with, provides, or includes access to an outdoor resource or facility.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a857b1481908ebfcf832c83376f |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:34 a.m.