Triple
T20654739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bindal River |
E507592
|
entity |
| Predicate | flowsDuring |
P140937
|
FINISHED |
| Object | monsoon season |
—
|
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: monsoon season | Statement: [Bindal River, flowsDuring, monsoon season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsDuring Context triple: [Bindal River, flowsDuring, monsoon season]
-
A.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
B.
flowsOver
Indicates that one substance or medium moves across the surface or boundary of another, covering or passing above it.
-
C.
flowsAcross
Indicates that one entity moves or extends in a continuous stream from one side of another entity to the other, traversing its area or boundary.
-
D.
flowsUnder
Indicates that one entity (typically a river, stream, or liquid) passes beneath another entity (such as a bridge, structure, or obstacle) along its course.
-
E.
flowsMostly
Indicates that one entity predominantly flows or moves in the direction of, or through, another entity, more so than in other directions or paths.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2ec90e881909250884483429acf |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:43 a.m.