Triple
T37172836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Donau |
E920959
|
entity |
| Predicate | operatedInWaters |
P84216
|
FINISHED |
| Object | North Sea |
E2599
|
NE 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: North Sea | Statement: [SS Donau, operatedInWaters, North Sea]
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 (4 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a020ec13d808190b41acdc31adc4191 |
completed | May 11, 2026, 5:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40360d62008190921d8a90b3e2c612 |
completed | June 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_6a020d9259c08190ad0370091c23ea8a |
completed | May 11, 2026, 5:10 p.m. |
Created at: May 3, 2026, 4:15 p.m.