Triple
T33823423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judith Merril |
E866893
|
entity |
| Predicate | usedPseudonymWith |
P177740
|
FINISHED |
| Object | C. M. Kornbluth |
—
|
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: C. M. Kornbluth | Statement: [Judith Merril, usedPseudonymWith, C. M. Kornbluth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPseudonymWith Context triple: [Judith Merril, usedPseudonymWith, C. M. Kornbluth]
-
A.
usedPseudonym
Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
-
B.
coAppearsWithPseudonym
Indicates that an entity appears together with another entity that is identified or referenced by a pseudonym in the same context or source.
-
C.
revealedAsPseudonymIn
Indicates that one identity or name is disclosed or recognized as a pseudonym within a particular context, work, or source.
-
D.
firstPublishedUnderPseudonym
Indicates that a work’s initial publication occurred under a pseudonym rather than the creator’s real name.
-
E.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
- F. None of above. chosen
Provenance (4 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:46 a.m.