Triple
T36764010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Mississippi River basin |
E908284
|
entity |
| Predicate | hasTypeOfDrainage |
P3833
|
FINISHED |
| Object | fluvial drainage |
—
|
LITERAL 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: fluvial drainage | Statement: [Middle Mississippi River basin, hasTypeOfDrainage, fluvial drainage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfDrainage Context triple: [Middle Mississippi River basin, hasTypeOfDrainage, fluvial drainage]
-
A.
hasDrainage
Indicates that one entity serves as the drainage system or outlet through which another entity’s liquid or runoff is removed or discharged.
-
B.
drainageType
chosen
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
-
C.
drainageStatus
Indicates the condition or effectiveness of water removal or runoff from an area, surface, or system.
-
D.
drainageInfluencedBy
Indicates that the pattern, direction, or effectiveness of drainage is affected or controlled by another factor or entity.
-
E.
drainageSystemIncludes
Indicates that a particular drainage system contains or encompasses a specified component, segment, or sub-system as part of its overall structure.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:12 p.m.