Triple
T6334083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Irwin |
E142448
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Irwin |
E113130
|
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: Irwin | Statement: [Bill Irwin, familyName, Irwin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Irwin Context triple: [Bill Irwin, familyName, Irwin]
-
A.
Irwin
chosen
Irwin is a masculine given name and surname of English origin, historically associated with various notable figures in fields such as entertainment, science, and politics.
-
B.
Irvin
Irvin is a surname most prominently associated with former NFL wide receiver and sports commentator Michael Irvin.
-
C.
Darvin
Darvin is a masculine given name most notably borne by former NBA player and current basketball coach Darvin Ham.
-
D.
Milhous
Milhous is the distinctive middle name of Richard Nixon, the 37th president of the United States.
-
E.
Erlich
Erlich is a variant spelling of the surname Ehrlich, which is of German origin and commonly associated with Jewish families.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06549084c8190b73fd94c9e0cb302 |
completed | March 22, 2026, 9:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c60424a5dc8190820970fce13776ac |
completed | March 27, 2026, 4:14 a.m. |
Created at: March 22, 2026, 4:30 p.m.