Triple
T29984829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle North Falls |
E761700
|
entity |
| Predicate | allowsWalkingBehindWaterfall |
P181426
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Middle North Falls, allowsWalkingBehindWaterfall, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsWalkingBehindWaterfall Context triple: [Middle North Falls, allowsWalkingBehindWaterfall, yes]
-
A.
waterfallAlong
Indicates that a waterfall is located along the course, path, or extent of another geographic feature such as a river, trail, or boundary.
-
B.
nearbyWaterfall
Indicates that the entity is located close to or within a short distance of a waterfall.
-
C.
hasTurbulentWatersBelow
Indicates that something is positioned above an area of water characterized by turbulence or strong, disturbed motion below it.
-
D.
canFall
Indicates that an entity has the potential or ability to fall or drop from a higher position to a lower one.
-
E.
hasWaterfall
Indicates that one entity possesses, contains, or features a waterfall associated with it.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: April 29, 2026, 6:36 p.m.