Triple
T25402447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ковальский |
E636460
|
entity |
| Predicate | связанный термин |
P111023
|
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.
relatedToTerm
chosen
Indicates a general, non-specific relationship or association between one term and another.
-
B.
повʼязанеЗ
Indicates a general association or connection between one entity and another.
-
C.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
D.
definitionOfRelatedConcept
Indicates that one concept provides the formal meaning, explanation, or characterization of another closely related concept.
-
E.
relatedIntermediate
Indicates an indirect or intermediate relationship between two entities, typically via one or more other entities or steps rather than a direct connection.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:52 p.m.