Triple
T27150149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mosquito River watershed |
E682364
|
entity |
| Predicate | waterFlowsToward |
P80269
|
FINISHED |
| Object | Mosquito River channel |
—
|
NE NERFINISHED |
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: Mosquito River channel | Statement: [Mosquito River watershed, waterFlowsToward, Mosquito River channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterFlowsToward Context triple: [Mosquito River watershed, waterFlowsToward, Mosquito River channel]
-
A.
waterFlowsThrough
Indicates that water moves along a path or channel passing from one location or object to another.
-
B.
waterwayDirection
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
-
C.
flowsToBodyOfWater
Indicates that a fluid or water source moves or is directed into a specified body of water.
-
D.
watercourseFor
chosen
Indicates that one entity serves as the watercourse (such as a river or channel) associated with, carrying, or draining another entity.
-
E.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 9:13 a.m.