Triple
T18400819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rusalka (character) |
E449986
|
entity |
| Predicate | relationshipToWater |
P130982
|
FINISHED |
| Object | daughter of the Water Goblin |
—
|
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: daughter of the Water Goblin | Statement: [Rusalka (character), relationshipToWater, daughter of the Water Goblin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToWater Context triple: [Rusalka (character), relationshipToWater, daughter of the Water Goblin]
-
A.
associatedWithWaterways
Indicates a relationship in which something is connected, linked, or relevant to waterways such as rivers, canals, or streams.
-
B.
touchesBodyOfWater
Indicates that one entity is in direct physical contact with the surface or boundary of a body of water.
-
C.
affectsWaterBody
Indicates that one entity has an impact on the condition, quality, or state of a water body.
-
D.
hasWaterResourceRole
Indicates that an entity participates in a water-related resource context with a specified functional role (e.g., source, user, manager, or regulator of water resources).
-
E.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
- F. None of above. chosen
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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e5194f2a8c8190afcd7db23e3795fb |
completed | April 19, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:46 a.m.