Triple
T26938073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamnik |
E678438
|
entity |
| Predicate | isPopularStartingPointFor |
P41494
|
FINISHED |
| Object | trips to Kamniška Bistrica Valley |
—
|
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: trips to Kamniška Bistrica Valley | Statement: [Kamnik, isPopularStartingPointFor, trips to Kamniška Bistrica Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularStartingPointFor Context triple: [Kamnik, isPopularStartingPointFor, trips to Kamniška Bistrica Valley]
-
A.
isStartingPointOf
chosen
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
-
B.
isPopularAt
Indicates that an entity enjoys a high level of recognition, approval, or favor within a specified place, context, or time.
-
C.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
-
D.
isPopularWith
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
-
E.
isGloballyPopular
Indicates that something is widely recognized, liked, or used by people across many different countries or regions.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 6:16 a.m.