Triple
T31276236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burgenstraße e.V. |
E797522
|
entity |
| Predicate | typeOfRouteMarketed |
P19187
|
FINISHED |
| Object | scenic tourist route |
—
|
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: scenic tourist route | Statement: [Burgenstraße e.V., typeOfRouteMarketed, scenic tourist route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRouteMarketed Context triple: [Burgenstraße e.V., typeOfRouteMarketed, scenic tourist route]
-
A.
marketedVia
Indicates that something is promoted, advertised, or sold through a particular channel, medium, or method.
-
B.
offeredOnRouteType
Indicates that a service or feature is provided specifically on routes of a particular type (e.g., bus, rail, express).
-
C.
primaryMarketedRouteName
Indicates the main route or method by which a product is marketed or delivered to its intended users.
-
D.
isBusinessRouteOf
Indicates that a route is designated primarily for business-related travel or access to commercial areas associated with a main route.
-
E.
notableRouteType
chosen
Indicates that a route is particularly significant or well-known for a specific type or category (e.g., scenic, historic, commercial).
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffbf84f4948190b41a7bba07ae61ec |
completed | May 9, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ffbf0a59f88190870dbe25d8a63a00 |
completed | May 9, 2026, 11:11 p.m. |
Created at: April 29, 2026, 9:13 p.m.