Triple
T11754160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lev Grossman |
E279482
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Lev |
E36954
|
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: Lev | Statement: [Lev Grossman, givenName, Lev]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lev Context triple: [Lev Grossman, givenName, Lev]
-
A.
Lev
chosen
Lev is the Russian given name of the renowned writer Leo Tolstoy, under which he was known in his native language.
-
B.
Lev
Lev is a young, brave former Seraphite who becomes a key companion to Abby in The Last of Us Part II, known for his resilience, archery skills, and struggle against his sect’s rigid beliefs.
-
C.
Leonid
Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
-
D.
Levin
Levin is a surname of Jewish origin borne by various notable individuals across fields such as business, politics, and the arts.
-
E.
Levin
Levin is a masculine given name of Germanic origin, historically borne by figures such as the Russian general Levin August von Bennigsen.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50b8a14819092a7397d73f0a8e3 |
completed | April 10, 2026, 7:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f01a21559c819097d0287dd8e2f411 |
completed | April 28, 2026, 2:23 a.m. |
Created at: April 8, 2026, 9:41 p.m.