Triple

T31568453
Position Surface form Disambiguated ID Type / Status
Subject SMTP Service Extension for 8bit-MIMEtransport E805482 entity
Predicate obsoletesRequirement P88548 FINISHED
Object strict 7-bit message body limitation in SMTP 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: strict 7-bit message body limitation in SMTP | Statement: [SMTP Service Extension for 8bit-MIMEtransport, obsoletesRequirement, strict 7-bit message body limitation in SMTP]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: obsoletesRequirement
Context triple: [SMTP Service Extension for 8bit-MIMEtransport, obsoletesRequirement, strict 7-bit message body limitation in SMTP]
  • A. isObsoleteFor chosen
    Indicates that something is no longer current, valid, or in use for a particular entity, context, or purpose.
  • B. previouslyRequired
    Indicates that one entity was required or necessary before another entity, typically as a prerequisite condition or step.
  • C. changesRequirement
    Indicates that one entity modifies, updates, or alters the requirements associated with another entity.
  • D. becameObsoleteWhen
    Indicates that one thing lost its relevance, usefulness, or validity at the time another specified event, condition, or entity came into existence or took effect.
  • E. retainsRequirement
    Indicates that one entity continues to hold or preserve a specific requirement associated with another entity.
  • 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_69f348d2ee94819091918d1789398c29 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a8055f8081908f635fe04654b5fe completed May 3, 2026, 1:42 a.m.
PD Predicate disambiguation batch_69f6a75656e081908739ed9e2f600e42 completed May 3, 2026, 1:39 a.m.
Created at: April 30, 2026, 10:18 p.m.