Triple
T32397169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potami waterfalls |
E827842
|
entity |
| Predicate | hasNumberOfCascades |
P178765
|
FINISHED |
| Object | series of cascades |
—
|
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: series of cascades | Statement: [Potami waterfalls, hasNumberOfCascades, series of cascades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfCascades Context triple: [Potami waterfalls, hasNumberOfCascades, series of cascades]
-
A.
hasNumberOfMainCascades
chosen
Indicates the relationship that specifies how many primary or main cascades (e.g., waterfall drops or major cascade segments) an entity possesses.
-
B.
isCascading
Indicates that one event, action, or effect triggers a chain of subsequent related events, actions, or effects.
-
C.
isMajorCascadeOf
Indicates that one event, process, or reaction is the primary or dominant cascade resulting from another, typically triggering a large-scale or critical chain of subsequent effects.
-
D.
hasNumberOfLevels
Indicates that an entity possesses a specified count of distinct levels or tiers.
-
E.
hasMultipleLevels
Indicates that something is organized into more than one hierarchical or structural level.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 1, 2026, 12:52 a.m.