Triple
T5744427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altmühl |
E126692
|
entity |
| Predicate | regionPopularFor |
P66487
|
FINISHED |
| Object | cycle tourism |
—
|
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: cycle tourism | Statement: [Altmühl, regionPopularFor, cycle tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionPopularFor Context triple: [Altmühl, regionPopularFor, cycle tourism]
-
A.
primaryRegionOfPopularity
Indicates the geographic region where something is most widely used, favored, or popular compared to other regions.
-
B.
regionPromoted
Indicates that a specific geographic or administrative region has been elevated to a higher status, priority, or level within a defined hierarchy or system.
-
C.
populationHubFor
Indicates a location that serves as a central concentration point or primary center for a population.
-
D.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
E.
isPopulousRegionOf
Indicates that a region has a large population and is located within or associated with a specified larger area or entity.
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02b4ea03c81908c3d799462de20c4 |
completed | March 22, 2026, 5:47 p.m. |
Created at: March 22, 2026, 3:48 p.m.