Triple
T13399960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Lawrence |
E319800
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Liebowitz |
E395147
|
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: Liebowitz | Statement: [Steve Lawrence, familyName, Liebowitz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Liebowitz Context triple: [Steve Lawrence, familyName, Liebowitz]
-
A.
Liebowitz
chosen
Liebowitz is a surname most notably associated with Ronald D. Liebowitz, an American academic administrator and university president.
-
B.
Horwitz
Horwitz is a German-French actor and singer known for his work in film, television, and theater, particularly in German-language productions.
-
C.
Loewenstein
Loewenstein is a surname of German origin associated with various notable individuals in fields such as science, politics, and the arts.
-
D.
Lipsitz
Lipsitz is a variant spelling of the Jewish surname Lifshitz, which has Ashkenazi origins.
-
E.
Levinstein
Levinstein is a surname of likely German or Ashkenazi Jewish origin, related etymologically to the name Löwenstein.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae47e99081909d8b5dba97a11988 |
completed | April 12, 2026, 2:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f730745a248190b32c11eeee618864 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 9:34 p.m.