Triple
T25583150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kudłoń |
E641307
|
entity |
| Predicate | hasScenicRoutes |
P162106
|
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: [Kudłoń, hasScenicRoutes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScenicRoutes Context triple: [Kudłoń, hasScenicRoutes, yes]
-
A.
hasScenicRouteType
Indicates that a route is associated with a specific type or category of scenic quality or scenic designation.
-
B.
hasScenicDrive
Indicates that one entity offers or features a visually appealing or picturesque driving route associated with it.
-
C.
hasScenicByway
Indicates that one place, route, or area is connected to or includes a designated scenic byway.
-
D.
hasScenicSections
Indicates that a route, path, or area contains segments that are visually attractive or offer notable scenic views.
-
E.
hasScenicPassNearby
Indicates that a location is situated close to a notable scenic pass, such as a mountain or landscape viewpoint route.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 21, 2026, 4:14 p.m.