Triple
T37429204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand River (Oklahoma) |
E930083
|
entity |
| Predicate | USGSName |
P187810
|
FINISHED |
| Object | Neosho River |
—
|
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: Neosho River | Statement: [Grand River (Oklahoma), USGSName, Neosho River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USGSName Context triple: [Grand River (Oklahoma), USGSName, Neosho River]
-
A.
USGSDesignation
Indicates that an entity has an official designation or classification assigned by the United States Geological Survey (USGS).
-
B.
USGSID
Indicates a unique identifier assigned by the U.S. Geological Survey to distinguish a specific geographic or geological feature from all others.
-
C.
geologicalSurveyCode
Indicates that an entity is associated with a specific identifier or code used in a geological survey to reference or catalog it.
-
D.
federalLandManager
Indicates that an entity serves as the managing authority or administrative body responsible for overseeing and regulating a particular area of federally owned land.
-
E.
basinAgency
Indicates that an agency has jurisdiction over, manages, or is responsible for a particular basin or watershed area.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.