Triple
T3688056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulde |
E78272
|
entity |
| Predicate | hasAverageDischargeClass |
P22889
|
FINISHED |
| Object | medium-sized river |
—
|
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: medium-sized river | Statement: [Mulde, hasAverageDischargeClass, medium-sized river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAverageDischargeClass Context triple: [Mulde, hasAverageDischargeClass, medium-sized river]
-
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.
drainageStatus
Indicates the condition or effectiveness of water removal or runoff from an area, surface, or system.
-
C.
dischargeRank
Indicates the rank or status an individual held at the time they were discharged from a role, service, or organization.
-
D.
drainageType
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
-
E.
hasDischarge
Indicates that one entity releases, emits, or expels a substance, energy, or flow from itself.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4c960788190b73ede08658846aa |
completed | March 8, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.