Triple
T13762628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladimir Krutov |
E330651
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Krutov |
E1050505
|
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: Krutov | Statement: [Vladimir Krutov, familyName, Krutov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Krutov Context triple: [Vladimir Krutov, familyName, Krutov]
-
A.
Krutov
chosen
Krutov is the namesake of a KLM airline route, likely a notable individual after whom the line was dedicated.
-
B.
Krupa
Krupa is a surname most famously associated with Gene Krupa, the pioneering American jazz and big band drummer.
-
C.
Lestkov
Lestkov is a small municipality and village located in the Tachov District of the Plzeň Region in the Czech Republic.
-
D.
Vaslav
Vaslav is the given name of Vaslav Nijinsky, the legendary early 20th-century ballet dancer and choreographer renowned for his groundbreaking work with the Ballets Russes.
-
E.
Kuzma
Kuzma is a masculine given name of Slavic origin, historically borne by notable figures such as the Russian national hero Kuzma Minin.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02250f4881908d5193b3d5d25844 |
completed | April 14, 2026, 9 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7a862e6808190b8fbb27304212058 |
completed | May 3, 2026, 7:56 p.m. |
Created at: April 9, 2026, 10:10 p.m.