Triple
T27536608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dassam Falls |
E695113
|
entity |
| Predicate | naturalAttractionType |
P158007
|
FINISHED |
| Object | scenic waterfall |
—
|
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: scenic waterfall | Statement: [Dassam Falls, naturalAttractionType, scenic waterfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: naturalAttractionType Context triple: [Dassam Falls, naturalAttractionType, scenic waterfall]
-
A.
naturalAttractionOf
Indicates a relationship where one entity is a natural feature or site that draws interest, attention, or visitors from another entity.
-
B.
naturalMonument
Indicates that something is designated as a natural monument, typically a protected natural feature of special scientific, cultural, or aesthetic significance.
-
C.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
D.
scenicCategory
chosen
Indicates the classification of a place or route based on its visual appeal or scenic qualities.
-
E.
geographicalNature
Indicates the natural geographic characteristics or physical landscape type associated with a place or region.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 1:29 p.m.