Triple
T389923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Pryor |
E8858
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Richard |
E19643
|
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: Richard | Statement: [Richard Pryor, givenName, Richard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Richard Context triple: [Richard Pryor, givenName, Richard]
-
A.
Richard
chosen
Richard is a common masculine given name of Germanic origin, widely used in English-speaking countries.
-
B.
Edward
Edward is a masculine given name of English origin, historically associated with kings of England and notable figures such as U.S. Senator Edward M. Kennedy.
-
C.
Charles
Charles is a masculine given name of Germanic origin that has been widely used across Europe and the English-speaking world, borne by numerous historical figures, royalty, and notable individuals.
-
D.
George
George is the first name of George Washington, the first President of the United States and a key leader in the American Revolutionary War.
-
E.
Roy
Roy is a common masculine given name of Celtic origin, often used independently or as a nickname for longer names.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5bdc848190826701590070497b |
completed | Feb. 28, 2026, 1:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a5778639448190937b8736b0006424 |
completed | March 2, 2026, 11:41 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.