Triple
T23928790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Лазарь Маркович Лисицкий |
E602432
|
entity |
| Predicate | сотрудничал с |
P80969
|
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.
συνεργάστηκεΜε
chosen
Indicates that one entity collaborated or worked together with another entity.
-
B.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
C.
frequentlyCollaboratedWith
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
-
D.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
E.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf9a18248190b20991969921ecfd |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:54 p.m.