Triple
T35434394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orest Kiprensky |
E1024159
|
entity |
| Predicate | notableWorkDepicts |
P147574
|
FINISHED |
| Object | Alexander Pushkin |
E22091
|
NE 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: Alexander Pushkin | Statement: [Orest Kiprensky, notableWorkDepicts, Alexander Pushkin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkDepicts Context triple: [Orest Kiprensky, notableWorkDepicts, Alexander Pushkin]
-
A.
notableWorkFeaturing
Indicates that a particular notable work (such as a book, film, or artwork) prominently includes, showcases, or is centered around a given entity.
-
B.
notableForDepicting
chosen
Indicates that something is recognized or distinguished specifically for portraying or representing a particular subject, theme, or scene.
-
C.
appearsInWorkOfArt
Indicates that an entity is depicted, represented, or otherwise featured within a particular work of art.
-
D.
notableWorkSubject
Indicates that a work is notably associated with a particular subject, such as a person, topic, or entity, as its primary focus or theme.
-
E.
depictsAuthorOf
Indicates that one entity visually represents or portrays the person who is the author of another entity.
- F. None of above.
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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3836bea6848190a93fc723d672e3bd |
completed | June 21, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.