Triple

T29762478
Position Surface form Disambiguated ID Type / Status
Subject Knorrhütte E753809 entity
Predicate typicalAccessTimeFrom P203926 FINISHED
Object about 4–5 hours from Garmisch-Partenkirchen via Reintal 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: about 4–5 hours from Garmisch-Partenkirchen via Reintal | Statement: [Knorrhütte, typicalAccessTimeFrom, about 4–5 hours from Garmisch-Partenkirchen via Reintal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalAccessTimeFrom
Context triple: [Knorrhütte, typicalAccessTimeFrom, about 4–5 hours from Garmisch-Partenkirchen via Reintal]
  • A. typicalAccessTimeFromImlil
    Indicates the usual amount of time it takes to travel from Imlil to a given destination or point of interest.
  • B. typicalTimes
    Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
  • C. accessedAt
    Indicates the time or date at which an entity was accessed or retrieved.
  • D. accessedFor
    Indicates that one entity is used to obtain entry to, retrieve, or make use of another entity.
  • E. typicalDurationMinutes
    Indicates the usual or expected length of time, measured in minutes, that an event, activity, or process typically lasts.
  • 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_69f0ef827ff88190ade56e0b0846b713 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_6a02f441bd408190923b6b68adee8fde completed May 12, 2026, 9:34 a.m.
PD Predicate disambiguation batch_6a02f3c1e64881908569423c9f298f26 completed May 12, 2026, 9:32 a.m.
PDg Predicate description generation batch_6a02f440f0e881909d669541aded3ca7 completed May 12, 2026, 9:34 a.m.
Created at: April 28, 2026, 8:34 p.m.