Triple
T19877361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glatt |
E477672
|
entity |
| Predicate | waterbodyTypeAtSource |
P1011
|
FINISHED |
| Object | lake outflow |
—
|
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: lake outflow | Statement: [Glatt, waterbodyTypeAtSource, lake outflow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterbodyTypeAtSource Context triple: [Glatt, waterbodyTypeAtSource, lake outflow]
-
A.
waterBodyTypeUpstream
Indicates that one water body is of a specified type and is located upstream relative to another water body or reference point.
-
B.
waterbodyType
chosen
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
C.
sourceOfWatercourse
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
D.
waterbodyID
Indicates a unique identifier that links an entity to a specific body of water.
-
E.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658dbdb648190b423865e7994a8fe |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.