Triple
T24692178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rennsteig |
E611469
|
entity |
| Predicate | hasAccommodationAlongRoute |
P120265
|
FINISHED |
| Object | guesthouses |
—
|
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: guesthouses | Statement: [Rennsteig, hasAccommodationAlongRoute, guesthouses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccommodationAlongRoute Context triple: [Rennsteig, hasAccommodationAlongRoute, guesthouses]
-
A.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
B.
hasAccommodationAtEndpoints
Indicates that the endpoints of something (e.g., a route, connection, or segment) each have available accommodation facilities.
-
C.
reservationLocatedAlong
Indicates that a reservation is situated along, adjacent to, or following the course or extent of a specified linear feature such as a road, river, or boundary.
-
D.
hasAlongRoute
chosen
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
E.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 3:20 a.m.