Triple
T8053070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poyang Lake |
E187721
|
entity |
| Predicate | waterLevelInfluencedBy |
P8157
|
FINISHED |
| Object | Yangtze River discharge |
—
|
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: Yangtze River discharge | Statement: [Poyang Lake, waterLevelInfluencedBy, Yangtze River discharge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterLevelInfluencedBy Context triple: [Poyang Lake, waterLevelInfluencedBy, Yangtze River discharge]
-
A.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
-
B.
waterMassInfluence
chosen
Indicates how the presence, amount, or distribution of water mass affects or modifies another entity or system.
-
C.
drainageInfluencedBy
Indicates that the pattern, direction, or effectiveness of drainage is affected or controlled by another factor or entity.
-
D.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
-
E.
reservoirElevation
Indicates the height or level of water stored in a reservoir relative to a defined reference point.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f7c425c8190aa1b2f534afeb58c |
completed | March 31, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.