Triple
T14784776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zola Jesus |
E347486
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Danilova |
E210550
|
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: Danilova | Statement: [Zola Jesus, familyName, Danilova]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Danilova Context triple: [Zola Jesus, familyName, Danilova]
-
A.
Danilova
chosen
Danilova is a Russian surname most famously associated with Alexandra Danilova, a celebrated 20th-century ballerina and influential ballet teacher.
-
B.
Danilovna
Danilovna is a Russian patronymic suffix used for women, indicating "daughter of Danil" or "daughter of Daniel."
-
C.
Lukyanova
Lukyanova is a Russian feminine surname derived from the masculine form Lukyanov.
-
D.
Tikhonova
Tikhonova is a Russian surname most prominently associated with Katerina Tikhonova, a public figure widely reported to be one of Vladimir Putin’s daughters.
-
E.
Zaitseva
Zaitseva is a common Russian feminine surname derived from the masculine form Zaitsev.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deca9f1c9c8190a8b28ba0ddd3e2e3 |
completed | April 14, 2026, 11:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe24b816388190be1127fe34a58d1d |
completed | May 8, 2026, 6 p.m. |
Created at: April 10, 2026, 1:31 a.m.