Triple
T38595277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kjeragbolten |
E934054
|
entity |
| Predicate | hikingRouteDuration |
P32784
|
FINISHED |
| Object | approximately 5–6 hours round trip |
—
|
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: approximately 5–6 hours round trip | Statement: [Kjeragbolten, hikingRouteDuration, approximately 5–6 hours round trip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hikingRouteDuration Context triple: [Kjeragbolten, hikingRouteDuration, approximately 5–6 hours round trip]
-
A.
hikeLength
Indicates the distance or duration associated with a hiking activity or trail.
-
B.
recommendedTimeToHike
Indicates the suggested or optimal time period during which one should undertake a particular hike.
-
C.
approximateHikeTimeRoundTrip
chosen
Indicates the estimated total time required to complete a hike from the starting point to the destination and back to the start.
-
D.
foragingTripDuration
Indicates the length of time an entity spends on a foraging trip before returning.
-
E.
showRouteDuration
Indicates that an entity displays or provides the duration required to traverse a specific route.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.