Triple
T22941216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Current River (Missouri) |
E569733
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Jacks Fork |
—
|
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: Jacks Fork | Statement: [Current River (Missouri), hasTributary, Jacks Fork]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jacks Fork Context triple: [Current River (Missouri), hasTributary, Jacks Fork]
-
A.
Jacks Fork River
chosen
Jacks Fork River is a clear, spring-fed river in the Missouri Ozarks known for its scenic bluffs, recreational floating, and inclusion within the Ozark National Scenic Riverways.
-
B.
Blue Fork
Blue Fork is a component of the multi-pronged weapon known as the Trident, likely representing one of its distinct forked tines.
-
C.
Barren Fork River
The Barren Fork River is a tributary of the Collins River in Middle Tennessee, known for its scenic float trips, fishing, and proximity to the city of McMinnville.
-
D.
Labette Creek
Labette Creek is a stream in southeastern Kansas whose name was adopted for Labette County.
-
E.
Greens Fork
Greens Fork is a small town in Wayne County, Indiana, known for its rural Midwestern character and historic roots.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181394fec81909da791bb346dbd0a |
completed | April 29, 2026, 3:55 a.m. |
Created at: April 17, 2026, 3:45 p.m.