Triple
T33483502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rasthof Frankenwald |
E857543
|
entity |
| Predicate | hasRestAreaFunction |
P29828
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rasthof Frankenwald, hasRestAreaFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestAreaFunction Context triple: [Rasthof Frankenwald, hasRestAreaFunction, yes]
-
A.
hasRestAreas
chosen
Indicates that a route, location, or facility includes one or more designated rest areas available for use.
-
B.
hasStopArea
Indicates that an entity is associated with or contains a specific stop area, such as a designated location where vehicles stop.
-
C.
hasRoadsideFacility
Indicates that a location or route segment is associated with a facility or service situated along its roadside.
-
D.
hasRegionalAmenity
Indicates that a region provides or contains a specific amenity or facility within its area.
-
E.
hasRestaurantArea
Indicates that a place or establishment includes a designated area used as a restaurant or for dining services.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:38 a.m.