Triple
T7775307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowenstein |
E221374
|
entity |
| Predicate | isRelatedToSurname |
P3889
|
FINISHED |
| Object | Levinstein |
E221376
|
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: Levinstein | Statement: [Lowenstein, isRelatedToSurname, Levinstein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Levinstein Context triple: [Lowenstein, isRelatedToSurname, Levinstein]
-
A.
Levinstein
chosen
Levinstein is a surname of likely German or Ashkenazi Jewish origin, related etymologically to the name Löwenstein.
-
B.
Rothstein
Rothstein is a Germanic-origin surname notably borne by individuals such as American photographer Arthur Rothstein.
-
C.
Loewenstein
Loewenstein is a surname of German origin associated with various notable individuals in fields such as science, politics, and the arts.
-
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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69caa4d005808190ac14c8d716421bdb |
completed | March 30, 2026, 4:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69caf5674c408190bdea241134fba474 |
completed | March 30, 2026, 10:12 p.m. |
Created at: March 30, 2026, 3:45 p.m.