Triple
T16246373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mala Osojnica |
E394380
|
entity |
| Predicate | hasViewReputation |
P122331
|
FINISHED |
| Object | iconic view of Lake Bled |
—
|
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: iconic view of Lake Bled | Statement: [Mala Osojnica, hasViewReputation, iconic view of Lake Bled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewReputation Context triple: [Mala Osojnica, hasViewReputation, iconic view of Lake Bled]
-
A.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
B.
hasQuirkyReputation
Indicates that an entity is regarded by others as having an unusual, eccentric, or unconventional character or style.
-
C.
crowdReputation
Indicates the collective opinion or perceived standing of an entity as judged by a group or general audience.
-
D.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
E.
hasPolicyReputationFor
Indicates that an entity is recognized or regarded in a particular way with respect to its policies or policy-related behavior.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245931074819096f38003da70f271 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.