Triple
T13051245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Schuster |
E327451
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Schuster |
E389423
|
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: Schuster | Statement: [Arthur Schuster, familyName, Schuster]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schuster Context triple: [Arthur Schuster, familyName, Schuster]
-
A.
Schuster
chosen
Schuster is a surname most notably associated with M. Lincoln Schuster, the American co-founder of the publishing company Simon & Schuster.
-
B.
Kutscher
Kutscher is a surname of German origin, often considered a variant spelling of Kutcher.
-
C.
Hufstedler
Hufstedler is the surname of Shirley Hufstedler, a prominent American judge and the first U.S. Secretary of Education.
-
D.
Schafer
Schafer is a surname of German origin borne by various notable individuals across fields such as entertainment, sports, and academia.
-
E.
Schultz
Schultz is a surname of German origin borne by numerous notable individuals across fields such as entertainment, politics, and academia.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980b98fa081908cfa92116799e874 |
completed | April 10, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6cbda9b548190a10a4835b2c75fdc |
completed | May 3, 2026, 4:15 a.m. |
Created at: April 9, 2026, 8:57 p.m.