Triple
T32456747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semily |
E829448
|
entity |
| Predicate | hasNotableSight |
P45300
|
FINISHED |
| Object | Jizera River valley |
—
|
NE NERFINISHED |
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: Jizera River valley | Statement: [Semily, hasNotableSight, Jizera River valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSight Context triple: [Semily, hasNotableSight, Jizera River valley]
-
A.
hasSights
chosen
Indicates that an entity possesses or features notable sights, attractions, or points of interest.
-
B.
containsNotablePlace
Indicates that one location includes within its boundaries a place that is considered notable or significant.
-
C.
hasNotableScenicSpot
Indicates that an entity possesses or is associated with a particularly remarkable or well-known scenic location.
-
D.
notableSpot
Indicates that a location is recognized as a significant or noteworthy place in some context.
-
E.
hasScenicViewOf
Indicates that one entity offers a visually appealing or picturesque view of another entity.
- 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0127c36dc08190b07765756b3d0e1b |
completed | May 11, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_6a0125ef57208190be5b5e761fcae981 |
completed | May 11, 2026, 12:42 a.m. |
Created at: May 1, 2026, 12:56 a.m.