Triple
T23730143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ham on Rye |
E586387
|
entity |
| Predicate | hasAlterEgoOfAuthor |
P86336
|
FINISHED |
| Object | Henry Chinaski |
—
|
NE NERFINISHED |
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: Henry Chinaski | Statement: [Ham on Rye, hasAlterEgoOfAuthor, Henry Chinaski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlterEgoOfAuthor Context triple: [Ham on Rye, hasAlterEgoOfAuthor, Henry Chinaski]
-
A.
hasFictionalAlterEgoOf
chosen
Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
-
B.
hasAuthorAlias
Indicates that an entity (such as a person or author record) is known by an alternative name or pseudonym used as an author.
-
C.
basedOnAuthorPseudonym
Indicates that something is derived from, inspired by, or determined using an author's pseudonym rather than their real name.
-
D.
revealedAsPseudonymIn
Indicates that one identity or name is disclosed or recognized as a pseudonym within a particular context, work, or source.
-
E.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
- F. None of above.
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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b9180bf48190a6c3656ef0530463 |
completed | April 29, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:09 p.m.