Triple
T34469807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | north-central Oklahoma |
E884874
|
entity |
| Predicate | partiallyDrainedBy |
P188465
|
FINISHED |
| Object | Arkansas River basin |
E1223353
|
NE FINISHED |
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: Arkansas River basin | Statement: [north-central Oklahoma, partiallyDrainedBy, Arkansas River basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyDrainedBy Context triple: [north-central Oklahoma, partiallyDrainedBy, Arkansas River basin]
-
A.
drainsPartOf
Indicates that one entity carries off or removes liquid or fluid from a specific part or portion of another entity.
-
B.
drainedIn
Indicates that a liquid, resource, or substance has flowed out from one entity and been discharged or emptied into another entity or location.
-
C.
drainedFrom
Indicates that a substance, resource, or liquid has been removed or emptied out from a particular source or container.
-
D.
drainedFor
Indicates that a resource, substance, or energy is removed from one entity for the benefit, use, or purpose of another entity.
-
E.
drainedDuring
Indicates that one entity had its resources, energy, or contents depleted in the course of another event or process.
- F. None of above. chosen
Provenance (5 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37212ffcf48190b556183ddd238767 |
completed | June 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 1, 2026, 2:01 a.m.