Triple
T25117048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inga Falls |
E629156
|
entity |
| Predicate | peakDischarge |
P54911
|
FINISHED |
| Object | can exceed 70,000 m³/s |
—
|
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: can exceed 70,000 m³/s | Statement: [Inga Falls, peakDischarge, can exceed 70,000 m³/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakDischarge Context triple: [Inga Falls, peakDischarge, can exceed 70,000 m³/s]
-
A.
maximumDischarge
chosen
Indicates the greatest allowable or observed rate at which something can be discharged or released from a source.
-
B.
peakEvent
Indicates the occurrence of a maximum or most intense point within a process, activity, or measurable phenomenon.
-
C.
peakUse
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
D.
peakType
Indicates the specific classification or category of a peak based on its form, prominence, or other defining characteristics.
-
E.
peakRating
Indicates the highest rating value that has been achieved or recorded for an entity over a given period or context.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465c7b88c81909fefbf647d1b810d |
completed | May 1, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:27 a.m.