Triple
T29798609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reintalangerhütte |
E756622
|
entity |
| Predicate | typicalAccessTimeFromValley |
P203926
|
FINISHED |
| Object | several hours on foot |
—
|
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: several hours on foot | Statement: [Reintalangerhütte, typicalAccessTimeFromValley, several hours on foot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAccessTimeFromValley Context triple: [Reintalangerhütte, typicalAccessTimeFromValley, several hours on foot]
-
A.
typicalAccessTimeFrom
chosen
Indicates the usual amount of time it takes to access or reach something starting from a specified source or location.
-
B.
typicalAccessTimeFromImlil
Indicates the usual amount of time it takes to travel from Imlil to a given destination or point of interest.
-
C.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
D.
hasValleyAccessTo
Indicates that one location can be reached from another specifically by traveling through a valley or valley-based route.
-
E.
typicalSettlementTime
Indicates the usual or expected amount of time it takes for a transaction or obligation to be fully settled.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a02fcbe03d0819082d3dd715ed41623 |
completed | May 12, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_6a02fc62138081908d2dbc5db7541d13 |
completed | May 12, 2026, 10:09 a.m. |
Created at: April 29, 2026, 5:17 p.m.