Triple
T13702106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levine |
E328543
|
entity |
| Predicate | hasRelatedSurname |
P3889
|
FINISHED |
| Object | Levine |
E328543
|
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: Levine | Statement: [Levine, hasRelatedSurname, Levine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Levine Context triple: [Levine, hasRelatedSurname, Levine]
-
A.
Levine
chosen
Levine is a common Jewish surname of Hebrew origin, often associated with descendants of the Levitical priestly class.
-
B.
Nat Levine
Nat Levine was an American film producer best known for founding Mascot Pictures and producing popular movie serials during the 1920s and 1930s.
-
C.
Levy
Levy is a variant spelling of the name Levi, commonly used as a Jewish surname and sometimes as a given name.
-
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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad162158819089280ee1e6b5c2cf |
completed | April 13, 2026, 8:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f794575d3881908de6ed988d848918 |
completed | May 3, 2026, 6:30 p.m. |
Created at: April 9, 2026, 9:54 p.m.