Triple
T26864827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotes Kloster |
E676435
|
entity |
| Predicate | bekanntFür |
P161540
|
FINISHED |
| Object | malerische Lage am Dunajec-Durchbruch |
—
|
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: malerische Lage am Dunajec-Durchbruch | Statement: [Rotes Kloster, bekanntFür, malerische Lage am Dunajec-Durchbruch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bekanntFür Context triple: [Rotes Kloster, bekanntFür, malerische Lage am Dunajec-Durchbruch]
-
A.
bekanntFür
chosen
Indicates that one entity is known or recognized for a particular quality, achievement, work, or characteristic associated with another entity.
-
B.
известенС
Indicates that one entity is known or recognized by another entity.
-
C.
известенКак
Indicates that one entity is known or recognized by a particular name, title, or role.
-
D.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
E.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:28 a.m.