Triple
T30949787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Нева |
E788503
|
entity |
| Predicate | mouthOfWaterSystem |
P4359
|
FINISHED |
| Object | Балтийское море |
—
|
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: Балтийское море | Statement: [Нева, mouthOfWaterSystem, Балтийское море]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthOfWaterSystem Context triple: [Нева, mouthOfWaterSystem, Балтийское море]
-
A.
mouthOfWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water or another watercourse.
-
B.
mouthOfTheWatercourse
chosen
Indicates the location where a watercourse ends and flows into a larger body of water.
-
C.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
D.
addressesWaterBody
Indicates that an action, plan, or measure is directed toward managing, affecting, or dealing with a specific water body.
-
E.
meetsWaterway
Indicates that one geographic feature or entity comes into contact with or joins a waterway such as a river, canal, or stream.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:53 p.m.