Triple
T26153772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alder Glen Campground |
E659899
|
entity |
| Predicate | popularityFor |
P3033
|
FINISHED |
| Object | fishing on the Nestucca River |
—
|
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: fishing on the Nestucca River | Statement: [Alder Glen Campground, popularityFor, fishing on the Nestucca River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularityFor Context triple: [Alder Glen Campground, popularityFor, fishing on the Nestucca River]
-
A.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
B.
popularityContext
Indicates the situational or domain-specific setting in which something’s popularity or level of public favor is evaluated.
-
C.
popularFor
chosen
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
-
D.
popularityRelativeTo
Indicates how the popularity of one entity compares to the popularity of another entity, typically in terms of being more, less, or equally popular.
-
E.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 26, 2026, 8:26 p.m.