Triple
T7132063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dzvina |
E166211
|
entity |
| Predicate | terminatesInBodyOfWaterType |
P75034
|
FINISHED |
| Object | sea |
—
|
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: sea | Statement: [Dzvina, terminatesInBodyOfWaterType, sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminatesInBodyOfWaterType Context triple: [Dzvina, terminatesInBodyOfWaterType, sea]
-
A.
locatedInBodyOfWater
Indicates that an entity is situated within or on the surface of a specific body of water.
-
B.
separatedFromByWaterBody
Indicates that two entities are apart from each other with a body of water lying between them as the separating barrier.
-
C.
isInlandWaterBodyOf
Indicates that one water body is an inland (non-oceanic) water feature that is geographically part of, contained within, or associated with another entity.
-
D.
adjacentToBodyOfWater
Indicates that one entity is directly next to or bordering a body of water, such as a lake, river, or ocean.
-
E.
locatedOnWaterbody
Indicates that an entity is situated on or directly adjacent to a specified body of water.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e66f15b88190bc1fb0f0a8af16a6 |
completed | March 27, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:45 p.m.