Triple
T7754894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poor Richard |
E175867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pseudonymous persona |
C2755
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: pseudonymous persona Context triple: [Poor Richard, instanceOf, pseudonymous persona]
-
A.
pseudonymous author
chosen
A pseudonymous author is a writer who publishes works under a fictitious name or alias instead of their real identity, often to separate different writing personas, protect privacy, or avoid social, political, or professional repercussions.
-
B.
pseudonymous informant
A pseudonymous informant is an individual who provides information or testimony while concealing their true identity behind a consistent but fictitious name or label.
-
C.
fictional persona
A fictional persona is an invented character with distinct traits, background, and motivations, created to embody perspectives or roles within a narrative or conceptual context.
-
D.
pseudonymous litigant
A pseudonymous litigant is a party to a legal proceeding who is permitted by the court to proceed under a fictitious or partially concealed name instead of their real identity, typically to protect privacy, safety, or other significant interests.
-
E.
fictionalized portrayal of real person
A fictionalized portrayal of a real person is a narrative representation that alters or embellishes factual details of an actual individual’s life, personality, or experiences for creative or dramatic purposes.
- F. None of above.
Provenance (1 batch)
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_69c6996180088190832e38e8d83ff54a |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4:08 p.m.