Triple

T19108108
Position Surface form Disambiguated ID Type / Status
Subject Lester Cole E467711 entity
Predicate wroteUnderBlacklist P71250 FINISHED
Object using fronts and pseudonyms LITERAL 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: using fronts and pseudonyms | Statement: [Lester Cole, wroteUnderBlacklist, using fronts and pseudonyms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wroteUnderBlacklist
Context triple: [Lester Cole, wroteUnderBlacklist, using fronts and pseudonyms]
  • A. blacklistedWriter
    Indicates that a writer has been officially banned or prohibited from participation, publication, or recognition by a person, group, or institution.
  • B. wasBlacklisted
    Indicates that an entity has been officially banned or excluded from participation, access, or consideration, typically due to disapproval or violation of rules.
  • C. blacklistedWriterUncredited chosen
    Indicates that a writer was involved in a work but, due to being blacklisted, was not officially credited.
  • D. wroteIn
    Indicates that an entity authored or composed something using a particular language, medium, or writing system.
  • E. wasCensored
    Indicates that an entity’s content, expression, or communication was suppressed, altered, or restricted by an authority or controlling party.
  • 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_69d8dd06a26481908039e2a1bae8c597 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e391f00c8190881a5977dd3728ed completed April 20, 2026, 8:28 a.m.
PD Predicate disambiguation batch_69e4b9ac41848190afd0f33b42cebe99 completed April 19, 2026, 11:17 a.m.
Created at: April 10, 2026, 12:04 p.m.