Triple
T8918295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans Reiser |
E212347
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Reiser |
E749728
|
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: Reiser | Statement: [Hans Reiser, familyName, Reiser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Reiser Context triple: [Hans Reiser, familyName, Reiser]
-
A.
Reiser
chosen
Reiser is a surname most notably associated with American actor, comedian, and writer Paul Reiser.
-
B.
Fiser
Fiser is a surname variant of Fischer, commonly associated with Central or Eastern European origins.
-
C.
Rainer
Rainer is a masculine given name of Germanic origin, related to names like Ragnar and Rayner, historically borne by various European nobles, clerics, and modern public figures.
-
D.
Scheider
Scheider is the surname of American actor Roy Scheider, best known for his role as Chief Brody in the film "Jaws."
-
E.
Sauer
Sauer is a German surname borne by various notable individuals in fields such as science, politics, and the arts.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66120eb08190913ab6c42f26ffb8 |
completed | April 1, 2026, 12:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfba49d65c8190b9d9908822198cc0 |
completed | April 3, 2026, 1:02 p.m. |
Created at: March 30, 2026, 6:56 p.m.