Triple
T37031156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Мухавец |
E916497
|
entity |
| Predicate | образуется при слиянии |
P402
|
FINISHED |
| Object | Россь |
—
|
NE NERFINISHED |
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.
partOfFormationOf
Indicates that one entity participates as a component or contributing element in the creation, development, or establishment of another entity.
-
B.
formedByUnionOf
chosen
Indicates that something is created or defined as the union or combination of multiple other things.
-
C.
mergerResultedIn
Indicates that a merger between entities led to the creation, change, or outcome represented by the related entity or state.
-
D.
depictsFormationOf
Indicates that one entity visually represents or illustrates the process by which another entity comes into existence or is formed.
-
E.
recombinedBy
Indicates that something (such as genetic material, data, or components) has been formed or altered through a recombination process carried out by a specified agent or mechanism.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.