Triple
T12563970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schneider |
E295419
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Schnider |
E295419
|
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: Schnider | Statement: [Schneider, hasVariant, Schnider]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schnider Context triple: [Schneider, hasVariant, Schnider]
-
A.
Schneider
chosen
Schneider is a German-origin surname commonly borne by people of German-speaking or Central European descent.
-
B.
Schaffner
Schaffner is a surname most notably associated with Franklin J. Schaffner, the Academy Award–winning American film director of works such as "Patton" and "Planet of the Apes."
-
C.
Scheider
Scheider is the surname of American actor Roy Scheider, best known for his role as Chief Brody in the film "Jaws."
-
D.
Schröder
Schröder is a common German surname borne by numerous notable figures in politics, sports, and the arts.
-
E.
Fiser
Fiser is a surname variant of Fischer, commonly associated with Central or Eastern European origins.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95494ae1c81908b9ee14b8ef92a65 |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6558da7e0819086860bfaf394e2d8 |
completed | May 2, 2026, 7:50 p.m. |
Created at: April 8, 2026, 11:49 p.m.