Triple
T9905920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Chop |
E185011
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Pittman |
E747700
|
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: Pittman | Statement: [Young Chop, familyName, Pittman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pittman Context triple: [Young Chop, familyName, Pittman]
-
A.
Pittman
chosen
Pittman is a surname of English origin borne by various notable individuals across politics, sports, and the arts.
-
B.
Penniman
Penniman is the surname of rock and roll pioneer Little Richard, whose full name was Richard Wayne Penniman.
-
C.
Hartman
Hartman is a surname of Germanic origin borne by various notable individuals across fields such as entertainment, academia, and politics.
-
D.
Mathieson
Mathieson is a surname of Scottish origin, typically regarded as a variant of Matheson and derived from a patronymic meaning “son of Matthew.”
-
E.
Paton
Paton is a surname and given name of Scottish origin, used by various notable individuals in fields such as sports, 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_69ca8296165881908ca4750701af1f29 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb50cf8808190a41e565216712704 |
completed | April 2, 2026, 12:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1eb316a188190a1c7fbe0d1997cf5 |
completed | April 5, 2026, 4:55 a.m. |
Created at: March 30, 2026, 8:40 p.m.