Triple
T14881383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cordelia Forebay |
E350006
|
entity |
| Predicate | basinUse |
P116183
|
FINISHED |
| Object | potable water conveyance support |
—
|
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: potable water conveyance support | Statement: [Cordelia Forebay, basinUse, potable water conveyance support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basinUse Context triple: [Cordelia Forebay, basinUse, potable water conveyance support]
-
A.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
-
B.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
C.
basinServed
Indicates that a particular basin is supplied, drained, or otherwise functionally supported by another entity (such as a river, watershed, or infrastructure system).
-
D.
resourceBasin
Indicates a relationship where a basin serves as a source or reservoir of resources for another entity or area.
-
E.
reservoirUse
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e7c0e48190af2d68a71130585c |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4c76e481909c0aa8d1a978e8d5 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:56 a.m.