Triple
T15123669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Bay |
E361229
|
entity |
| Predicate | hasScenicViewpointsAt |
P96770
|
FINISHED |
| Object | hills above Duluth |
—
|
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: hills above Duluth | Statement: [St. Louis Bay, hasScenicViewpointsAt, hills above Duluth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScenicViewpointsAt Context triple: [St. Louis Bay, hasScenicViewpointsAt, hills above Duluth]
-
A.
hasScenicViewpoints
chosen
Indicates that something includes or provides locations specifically intended for enjoying scenic or panoramic views.
-
B.
hasScenicViewOf
Indicates that one entity offers a visually appealing or picturesque view of another entity.
-
C.
isPartOfScenicVista
Indicates that something is included within, or contributes to, a larger scenic vista or panoramic view.
-
D.
hasSummitViewsOf
Indicates that from the summit of one location, there are views overlooking or directed toward another location.
-
E.
hasScenicAccessTo
Indicates that one place or object provides a visually appealing or notable view of another place or object.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005a0c6888190840de4ead2306544 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.