Triple
T33116533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chekhov |
E847471
|
entity |
| Predicate | namedAfterWorkDomain |
P63
|
FINISHED |
| Object | Russian literature |
—
|
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: Russian literature | Statement: [Chekhov, namedAfterWorkDomain, Russian literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterWorkDomain Context triple: [Chekhov, namedAfterWorkDomain, Russian literature]
-
A.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
-
B.
formerDomain
Indicates that one entity was previously the domain or area of control, influence, or ownership of another entity, but no longer is.
-
C.
associatedNicknameOfWork
Indicates that a given nickname or informal title is commonly used to refer to a particular work.
-
D.
namedForWork
Indicates that one entity is named in honor of, or derived from the title of, a particular work (such as a book, film, artwork, or other creative production).
-
E.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:27 a.m.