Triple
T19447400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Werner R. Heymann |
E486515
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Heymann |
—
|
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: Heymann | Statement: [Werner R. Heymann, familyName, Heymann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heymann Context triple: [Werner R. Heymann, familyName, Heymann]
-
A.
Heymann
chosen
Heymann is a surname most notably associated with Philip B. Heymann, an influential American legal scholar and former U.S. Deputy Attorney General.
-
B.
Heyman
Heyman is a surname most prominently associated with British film producer David Heyman, known for producing the Harry Potter film series.
-
C.
Heumann
Heumann is the surname of Judith Heumann, a pioneering American disability rights activist and leader in the independent living movement.
-
D.
Youmans
Youmans is a surname most notably associated with American Broadway composer Vincent Youmans, known for classic songs from the early 20th century.
-
E.
Hammann
Hammann is a German-origin surname borne by various notable individuals in fields such as aviation, music, and academia.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338b25d88190bc137a411576c73f |
completed | April 20, 2026, 2:09 p.m. |
Created at: April 10, 2026, 1:38 p.m.