Triple
T20956997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conrad Richter |
E516127
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Richter |
—
|
NE NERFINISHED |
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: Richter | Statement: [Conrad Richter, familyName, Richter]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Richter Context triple: [Conrad Richter, familyName, Richter]
-
A.
Richter
chosen
Richter is a common German surname borne by numerous notable individuals, including artists, scientists, and public figures.
-
B.
Rikter Bedan
Rikter Bedan is a notable literary work by Bengali poet and revolutionary Kazi Nazrul Islam, reflecting his characteristic themes of rebellion and humanism.
-
C.
Reiser
Reiser is a surname most notably associated with American actor, comedian, and writer Paul Reiser.
-
D.
Rigler
Rigler is a surname most notably associated with Cy Rigler, an early 20th-century American Major League Baseball umpire.
-
E.
Heinrichs
Heinrichs is a German-origin surname borne by various notable individuals, including Finnish general Erik Heinrichs.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb6c2f1481908360fb86d2b6a8e4 |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 1:28 p.m.