Triple
T30064187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drake Falls |
E763980
|
entity |
| Predicate | hasYearRoundFlow |
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: [Drake Falls, hasYearRoundFlow, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYearRoundFlow Context triple: [Drake Falls, hasYearRoundFlow, true]
-
A.
accessibleYearRound
Indicates that the subject can be accessed or used during all seasons of the year without interruption.
-
B.
hasSeasonalRound
Indicates a recurring, seasonally patterned cycle of movements, activities, or resource use associated with an entity over the course of a year.
-
C.
operatedYearRound
Indicates that the subject entity functioned or was in operation continuously throughout the entire year, without seasonal closure.
-
D.
isUsedAllYear
Indicates that something is utilized or remains in active use throughout the entire year, without being limited to a particular season or period.
-
E.
openedForYearRoundTraffic
Indicates that something has been made accessible and usable for traffic throughout the entire year, without seasonal closures.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ca5a1008190880f6da9f69c263b |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 6:58 p.m.