Triple
T21646091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domhütte |
E534219
|
entity |
| Predicate | servesAsBaseForRoute |
P144829
|
FINISHED |
| Object | normal route on Dom |
—
|
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: normal route on Dom | Statement: [Domhütte, servesAsBaseForRoute, normal route on Dom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsBaseForRoute Context triple: [Domhütte, servesAsBaseForRoute, normal route on Dom]
-
A.
servesAsRouteTo
Indicates that one entity functions as a pathway, channel, or means of access leading to another entity.
-
B.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
C.
isRelatedRouteOf
Indicates that one route is connected to, associated with, or serves as an alternative or complementary path to another route.
-
D.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
-
E.
routingBasis
Indicates the principle or criterion used to determine how something is directed, routed, or assigned among possible paths or destinations.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5394c570819081dbbe7e0f98f7d3 |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:35 p.m.