Triple
T1234412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waal |
E26512
|
entity |
| Predicate | hasAverageDischarge |
P22889
|
FINISHED |
| Object | one of the highest in the Netherlands |
—
|
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: one of the highest in the Netherlands | Statement: [Waal, hasAverageDischarge, one of the highest in the Netherlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAverageDischarge Context triple: [Waal, hasAverageDischarge, one of the highest in the Netherlands]
-
A.
dischargeAverage
chosen
Indicates the typical or mean rate at which something (such as fluid, electricity, or emissions) is released or flows over a given period.
-
B.
hasDischarge
Indicates that one entity releases, emits, or expels a substance, energy, or flow from itself.
-
C.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
D.
hasSpillway
Indicates that a dam or similar water-retaining structure is equipped with a spillway for controlled release or overflow of water.
-
E.
dischargeRank
Indicates the rank or status an individual held at the time they were discharged from a role, service, or organization.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be5e421081908f2432528019db25 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.