Triple
T16650403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1938 Yellow River flood |
E404586
|
entity |
| Predicate | riverCourseChange |
P77322
|
FINISHED |
| Object | diverted Yellow River southward |
—
|
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: diverted Yellow River southward | Statement: [1938 Yellow River flood, riverCourseChange, diverted Yellow River southward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverCourseChange Context triple: [1938 Yellow River flood, riverCourseChange, diverted Yellow River southward]
-
A.
riverbedDivertedTo
Indicates that the natural course of a riverbed has been redirected or channeled toward another location or pathway.
-
B.
riverDivertedTo
chosen
Indicates that the natural course of a river has been intentionally redirected from its original path to a new channel or destination.
-
C.
riverFormed
Indicates that a river came into existence or was created, typically as a result of natural geological or hydrological processes.
-
D.
riverConfluence
Indicates the location or relationship where two or more rivers or streams join and merge into a single watercourse.
-
E.
riverPhenomenon
Indicates a natural event, condition, or process that occurs in or directly affects a river.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bf6cfc481909b183348c407e046 |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.