Triple
T16577347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Jaspers |
E402745
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Jaspers |
E402745
|
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: Jaspers | Statement: [Karl Jaspers, familyName, Jaspers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jaspers Context triple: [Karl Jaspers, familyName, Jaspers]
-
A.
Jaspers
chosen
Jaspers is a German surname most notably associated with the existentialist philosopher and psychiatrist Karl Jaspers.
-
B.
Jansen
Jansen is a member of the German musical group Bangert, Jansen, Scholz, Schultes.
-
C.
Opsarius
Opsarius is a genus of small freshwater cyprinid fishes native to rivers and streams of South and Southeast Asia.
-
D.
Hufstedler
Hufstedler is the surname of Shirley Hufstedler, a prominent American judge and the first U.S. Secretary of Education.
-
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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3595dd90881909933216bd12505e1 |
completed | April 18, 2026, 10:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006eecbb6c81908abc5659333a4879 |
completed | May 10, 2026, 11:41 a.m. |
Created at: April 10, 2026, 5:16 a.m.