Triple
T25168384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Fork Eel River |
E630244
|
entity |
| Predicate | confluenceWithEelRiverNear |
P157273
|
FINISHED |
| Object | Dyerville, California |
—
|
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: Dyerville, California | Statement: [South Fork Eel River, confluenceWithEelRiverNear, Dyerville, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confluenceWithEelRiverNear Context triple: [South Fork Eel River, confluenceWithEelRiverNear, Dyerville, California]
-
A.
locatedAtConfluenceOf
Indicates that something is situated at the meeting point where two or more bodies of water or similar flowing features join together.
-
B.
riverConfluence
Indicates the location or relationship where two or more rivers or streams join and merge into a single watercourse.
-
C.
joinsRiverNear
chosen
Indicates that one river or watercourse flows into and merges with another river at or close to a specified location.
-
D.
locatedOnTributaryOf
Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
-
E.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d43e6d08190bbd8643ea058ceea |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:18 p.m.