Triple

T34068087
Position Surface form Disambiguated ID Type / Status
Subject Cyril Judd E873683 entity
Predicate collaborativePseudonymFor P177740 FINISHED
Object Cyril M. Kornbluth and Judith Merril 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: Cyril M. Kornbluth and Judith Merril | Statement: [Cyril Judd, collaborativePseudonymFor, Cyril M. Kornbluth and Judith Merril]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: collaborativePseudonymFor
Context triple: [Cyril Judd, collaborativePseudonymFor, Cyril M. Kornbluth and Judith Merril]
  • 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. pseudonymForRole
    Indicates that a pseudonym is used specifically when an entity is acting in a particular role or capacity.
  • C. usedPseudonymWith chosen
    Indicates that one entity employed a pseudonym or alias when interacting or being associated with another entity.
  • D. pseudonymCoinedBy
    Indicates that a particular pseudonym was created or invented by a specific agent or source.
  • E. addresseePseudonym
    Indicates that the referenced name is a pseudonym used for the addressee in the context of the described communication or interaction.
  • 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_69f349a4af208190afa14888f9c9fb9d completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f70ba61fac81909f614db6c36b1103 completed May 3, 2026, 8:47 a.m.
PD Predicate disambiguation batch_69f70ac0170c819098e3b8e41d02efef completed May 3, 2026, 8:43 a.m.
Created at: May 1, 2026, 1:52 a.m.