Triple
T11865746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schlenze (nearby watercourse) |
E282277
|
entity |
| Predicate | hasWatertype |
P92225
|
FINISHED |
| Object | freshwater |
—
|
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: freshwater | Statement: [Schlenze (nearby watercourse), hasWatertype, freshwater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWatertype Context triple: [Schlenze (nearby watercourse), hasWatertype, freshwater]
-
A.
hasWaterFeatures
Indicates that an entity includes or is associated with water-related elements such as fountains, ponds, streams, or similar features.
-
B.
hasBodyOfWaterType
chosen
Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
-
C.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
D.
hasWaterBodyCharacteristic
Indicates that a water body possesses a specified physical, chemical, or ecological characteristic.
-
E.
waterContains
Indicates that a body or volume of water holds, includes, or has within it a specified substance, object, or entity.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73a233081909449ab294d01a512 |
completed | April 10, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69d8a2589f0c8190ad82ff11acabae93 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.