Triple
T21960769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lise Khokhlakova |
E542320
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Khokhlakova |
—
|
NE NERFINISHED |
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: Khokhlakova | Statement: [Lise Khokhlakova, familyName, Khokhlakova]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khokhlakova Context triple: [Lise Khokhlakova, familyName, Khokhlakova]
-
A.
Khokhlova
chosen
Khokhlova is a Russian surname most famously borne by Olga Khokhlova, a Ukrainian-Russian ballerina and the first wife of Pablo Picasso.
-
B.
Khovrino
Khovrino is a Moscow Metro station serving as the northern terminus of the Zamoskvoretskaya Line.
-
C.
Kuntsevskaya
Kuntsevskaya is a Moscow Metro station on the Big Circle Line serving the Kuntsevo District in western Moscow.
-
D.
Volkova
Volkova is a Russian surname commonly borne by individuals of Slavic origin, including notable figures in politics, arts, and sciences.
-
E.
Skobelevskaya
Skobelevskaya is a Moscow Metro station serving the Severnoye Butovo District in the south of Moscow.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12455e99c819092ec59fe571f814e |
completed | April 28, 2026, 9:19 p.m. |
Created at: April 16, 2026, 8 p.m.