Triple
T10579532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Wayne Penniman |
E249697
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Penniman |
E249697
|
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: Penniman | Statement: [Richard Wayne Penniman, familyName, Penniman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Penniman Context triple: [Richard Wayne Penniman, familyName, Penniman]
-
A.
Penniman
chosen
Penniman is the surname of rock and roll pioneer Little Richard, whose full name was Richard Wayne Penniman.
-
B.
Pittman
Pittman is a surname of English origin borne by various notable individuals across politics, sports, and the arts.
-
C.
Hooperman
Hooperman is an American television dramedy series from the late 1980s starring John Ritter as a San Francisco police inspector balancing his personal and professional life.
-
D.
Payne
Payne is a small community located within Bibb County in the state of Georgia, United States.
-
E.
Payne
Payne is a common English surname of Norman origin, historically derived from the medieval given name "Pagan" or "Payne."
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52757b870819085b03aa6805aa076 |
completed | April 7, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d95e78ad6c81909eaa0cdc41c5cc82 |
completed | April 10, 2026, 8:32 p.m. |
Created at: April 6, 2026, 12:38 p.m.