Triple
T18840378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonlé Sap Lake |
E460776
|
entity |
| Predicate | floodPulse |
P107961
|
FINISHED |
| Object | monsoon-driven annual flood pulse |
—
|
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-driven annual flood pulse | Statement: [Tonlé Sap Lake, floodPulse, monsoon-driven annual flood pulse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodPulse Context triple: [Tonlé Sap Lake, floodPulse, monsoon-driven annual flood pulse]
-
A.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
B.
floodType
chosen
Indicates the specific kind or category of flooding involved in an event or situation.
-
C.
floodGauge
Indicates that a device or measurement point is used to monitor and record the level or intensity of flooding at a specific location.
-
D.
floodStage
Indicates that a water body’s level has reached or exceeded the defined height at which flooding is expected to begin or become hazardous.
-
E.
floodPeakDischarge
Indicates the maximum rate of water flow occurring at the peak of a flood event in a river or channel.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8e8f57081909edbbcaf56189816 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.