Triple
T29975293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levshitz |
E761427
|
entity |
| Predicate | notableBearerFamilyName |
P202111
|
FINISHED |
| Object | Evgeny Lifshitz |
E418495
|
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: Evgeny Lifshitz | Statement: [Levshitz, notableBearerFamilyName, Evgeny Lifshitz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBearerFamilyName Context triple: [Levshitz, notableBearerFamilyName, Evgeny Lifshitz]
-
A.
notableBearerFullName
Indicates that a full personal name is that of a notable or well-known bearer associated with the referenced entity.
-
B.
hasNotableBearerSurname
chosen
Indicates that a surname is associated with at least one notable or well-known individual who bears it.
-
C.
hasNotableBearerFamily
Indicates that a family is recognized for having at least one notable or distinguished member associated with it.
-
D.
notableFamilyNameOf
Indicates that a particular family name is notably or prominently associated with a given person or family entity.
-
E.
notableBearerVariantOf
Indicates that one entity is a notable or prominent variant or version of another entity that bears or carries its characteristics.
- F. None of above.
Provenance (4 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2757f495b881909da6432998c2c4da |
completed | June 9, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 6:33 p.m.