Triple
T19846474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Руза |
E476871
|
entity |
| Predicate | берега |
P26064
|
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: [Руза, берега, преимущественно лесистые]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: берега Context triple: [Руза, берега, преимущественно лесистые]
-
A.
bayOf
Indicates that one location is a bay that forms an inlet or coastal indentation associated with another geographic entity, such as a sea, ocean, or coastline.
-
B.
shore
chosen
Indicates a relationship where one entity forms or lies along the edge or boundary of a body of water, such as a sea, lake, or river.
-
C.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
-
D.
bay
Indicates that one entity howls or barks loudly, often repeatedly, typically in reaction to something such as prey, the moon, or a disturbance.
-
E.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65809da2c8190bb579ef42513b74d |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.