Triple
T25402444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ковальский |
E636460
|
entity |
| Predicate | использование в ономастике |
P158483
|
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.
exerciseOf
Indicates the performance or carrying out of a right, power, function, or activity by an entity.
-
B.
usedInExerciseType
Indicates that something (e.g., an item, movement, or technique) is employed as part of a particular type or category of exercise.
-
C.
Bewegung
Indicates a movement or change of position or location of an entity relative to a reference point or path.
-
D.
usedInSport
Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
-
E.
используетсяС
Indicates that something is used together with or by means of another entity.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584fbde0c8190ac451fe33848aadb |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:52 p.m.