Triple
T5925916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilya Tolstoy |
E131809
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Sergei Tolstoy |
E542525
|
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: Sergei Tolstoy | Statement: [Ilya Tolstoy, sibling, Sergei Tolstoy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sergei Tolstoy Context triple: [Ilya Tolstoy, sibling, Sergei Tolstoy]
-
A.
Sergei Tolstoy
Sergei Tolstoy was a Russian nobleman and musician, best known as a son of the writer Leo Tolstoy and a member of the prominent Tolstoy family.
-
B.
Andrey Tolstoy
Andrey Tolstoy is an early patrilineal ancestor of the prominent Russian noble Tolstoy family.
-
C.
Alexei Tolstoy
Alexei Tolstoy was a prominent Russian writer and novelist known for his historical epics, science fiction works, and contributions to Soviet literature.
-
D.
Sergei Lvovich Tolstoy
chosen
Sergei Lvovich Tolstoy was a Russian musician, composer, and translator, best known as the eldest son of the writer Leo Tolstoy and for promoting his father’s literary legacy.
-
E.
Ilya Tolstoy
Ilya Tolstoy was a member of the prominent Russian Tolstoy family, known primarily as a descendant of the famed writer Leo Tolstoy.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c038542e548190b335df9a948c8490 |
completed | March 22, 2026, 6:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6409a1b588190a963b0f6944ba22c |
completed | March 27, 2026, 8:32 a.m. |
Created at: March 22, 2026, 4 p.m.