Triple
T33242051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumberland Falls |
E850987
|
entity |
| Predicate | flowsYearRound |
P168403
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cumberland Falls, flowsYearRound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsYearRound Context triple: [Cumberland Falls, flowsYearRound, true]
-
A.
flowsAround
Indicates that one entity moves in a continuous, typically fluid motion encircling or passing on multiple sides around another entity.
-
B.
flowsMostly
Indicates that one entity predominantly flows or moves in the direction of, or through, another entity, more so than in other directions or paths.
-
C.
flowsDuring
Indicates that one process, event, or activity occurs within or throughout the time span of another.
-
D.
hasYearRoundFlow
chosen
Indicates that the related water body or flow system maintains continuous discharge throughout the entire year without drying up seasonally.
-
E.
flowsAcross
Indicates that one entity moves or extends in a continuous stream from one side of another entity to the other, traversing its area or boundary.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:31 a.m.