Triple
T17850918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palouse River |
E445801
|
entity |
| Predicate | mouthLocatedInCounty |
P23957
|
FINISHED |
| Object | Franklin County, Washington |
—
|
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: Franklin County, Washington | Statement: [Palouse River, mouthLocatedInCounty, Franklin County, Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthLocatedInCounty Context triple: [Palouse River, mouthLocatedInCounty, Franklin County, Washington]
-
A.
mouthLocatedInAdministrativeEntity
Indicates that the place where a river ends (its mouth) is situated within a specific administrative region or jurisdiction.
-
B.
locatedInCountySeatOfCounty
Indicates that one entity is located in the county seat city or town of the specified county.
-
C.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
-
D.
locatedInCountyRegion
Indicates that one entity is geographically situated within the boundaries of a specific county or county-level region.
-
E.
inCounty
chosen
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ffe415c8190aed351c52b78a143 |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.