Triple
T34206341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snoqualmie Falls |
E877519
|
entity |
| Predicate | viewingAreaLocation |
P76038
|
FINISHED |
| Object | rim of the gorge |
—
|
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: rim of the gorge | Statement: [Snoqualmie Falls, viewingAreaLocation, rim of the gorge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewingAreaLocation Context triple: [Snoqualmie Falls, viewingAreaLocation, rim of the gorge]
-
A.
uiLocation
Indicates the on-screen position or placement of a user interface element within a UI layout or display.
-
B.
locationOfVision
Indicates the place or setting where a vision or visual experience occurs or is perceived.
-
C.
locationPresented
Indicates that a specific location is presented or shown to an entity (such as a user or system) within a given context.
-
D.
objectLocation
chosen
Indicates that one entity is located at, in, or on another entity or spatial region.
-
E.
reportingArea
Indicates that one entity serves as the geographic or organizational area for which information, data, or events about another entity are reported or aggregated.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7105085fc81909ece409d01619f82 |
completed | May 3, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.