Triple
T31555227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Дзига Вертов |
E805108
|
entity |
| Predicate | частый соавтор |
P129005
|
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.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
-
B.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
C.
frequentlyCollaboratedWith
chosen
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
-
D.
coAuthorshipType
Indicates the specific nature or category of the collaborative authorship relationship between two or more contributors.
-
E.
primaryCollaborator
Indicates that one entity serves as the main or most significant partner working jointly with another entity on a shared activity, project, or goal.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:12 p.m.