Triple
T23280778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sofya Tolstaya |
E588853
|
entity |
| Predicate | roleInLeoTolstoysWork |
P15535
|
FINISHED |
| Object | copyist of manuscripts |
—
|
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: copyist of manuscripts | Statement: [Sofya Tolstaya, roleInLeoTolstoysWork, copyist of manuscripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInLeoTolstoysWork Context triple: [Sofya Tolstaya, roleInLeoTolstoysWork, copyist of manuscripts]
-
A.
roleInWarAndPeace
Indicates that an entity has a specific role or function within the context of the War and Peace conflict or narrative.
-
B.
roleInAnalects
Indicates that one entity has a specific role, function, or status within the context of the Analects.
-
C.
literaryRole
chosen
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
D.
biblicalFigureRole
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
E.
roleInActs
Indicates the specific function or character that an entity performs or portrays within one or more acts or performances.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19642b46481909fd455acd2155792 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:56 p.m.