Triple
T22287454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoopa Valley |
E550899
|
entity |
| Predicate | isWithinWatershed |
P17416
|
FINISHED |
| Object | Trinity River watershed |
—
|
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: Trinity River watershed | Statement: [Hoopa Valley, isWithinWatershed, Trinity River watershed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWithinWatershed Context triple: [Hoopa Valley, isWithinWatershed, Trinity River watershed]
-
A.
hasWatershedWith
Indicates that two geographic areas share or are associated with the same watershed or drainage basin.
-
B.
isInCatchment
Indicates that one entity lies within the geographic or service area covered or served by another entity.
-
C.
hasWatershed
chosen
Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
-
D.
liesOnWatershedBetween
Indicates that something is located on or along the dividing line between two drainage basins or watersheds.
-
E.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560896348190985725ac8ad406b3 |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.