Triple
T37172836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Donau |
E920959
|
entity |
| Predicate | operatedInWaters |
—
|
GENERATED |
| Object | North Sea |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInWaters Context triple: [SS Donau, operatedInWaters, North Sea]
-
A.
operatedOnWaterBody
chosen
Indicates that an entity performs its operation or activity on or in a specific body of water.
-
B.
tookPlaceInBodyOfWater
Indicates that an event or action occurred within or on a specific body of water.
-
C.
appliesToTerritorialWatersOf
Indicates that something (such as a rule, status, or condition) is applicable within the territorial waters of a specified entity.
-
D.
hasNearbyWatersUsedBy
Indicates that a body of water located near an entity is utilized or accessed by another specified entity.
-
E.
hasWatersOf
Indicates that a geographic or physical entity contains, is traversed by, or is otherwise characterized by specific bodies or types of water.
- F. None of above.
Provenance (1 batch)
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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.