Triple
T26070751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frognerseteren station |
E657536
|
entity |
| Predicate | summerUsage |
P159915
|
FINISHED |
| Object | popular for hiking access |
—
|
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: popular for hiking access | Statement: [Frognerseteren station, summerUsage, popular for hiking access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summerUsage Context triple: [Frognerseteren station, summerUsage, popular for hiking access]
-
A.
summerPeak
Indicates that something reaches its highest level, intensity, or activity during the summer season.
-
B.
summerAccess
Indicates that an entity is permitted to use or enter a resource, place, or service specifically during the summer period.
-
C.
summerHomeOf
Indicates that a location serves as a seasonal or vacation residence for a person or group, specifically used during the summer.
-
D.
summerBase
Indicates a base or location where an entity is situated or operates specifically during the summer season.
-
E.
summerTouristSeason
Indicates the period during summer when a place experiences increased tourist activity or visitation.
- F. None of above. chosen
Provenance (4 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606ca69b08190977693fd1f8e8ae4 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 7:28 p.m.