Triple
T23584866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheoah River |
E582313
|
entity |
| Predicate | hasScheduledReleases |
P152804
|
FINISHED |
| Object | for whitewater recreation |
—
|
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: for whitewater recreation | Statement: [Cheoah River, hasScheduledReleases, for whitewater recreation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScheduledReleases Context triple: [Cheoah River, hasScheduledReleases, for whitewater recreation]
-
A.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
B.
hasReleased
Indicates that an entity has made another entity publicly available or officially launched it.
-
C.
hasWorkReleasedIn
Indicates that a creative work (such as a book, film, or album) was released or made publicly available in a particular time period or location.
-
D.
hasReleaseBranch
Indicates that an entity is associated with a specific release branch, typically representing a stabilized version line in a version control or release management system.
-
E.
supportsReleasesOf
Indicates that one entity provides assistance, resources, or endorsement for the publication or rollout of another entity’s releases.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02f68288190b348c7558a6a24e1 |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:40 p.m.