Triple

T5919742
Position Surface form Disambiguated ID Type / Status
Subject Let’s Encrypt E131670 entity
Predicate supportsValidation P23074 FINISHED
Object domain control validation 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: domain control validation | Statement: [Let’s Encrypt, supportsValidation, domain control validation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsValidation
Context triple: [Let’s Encrypt, supportsValidation, domain control validation]
  • A. supportsValidationOf chosen
    Indicates that one entity provides the mechanisms or conditions necessary for another entity to be checked or verified for correctness or compliance.
  • B. supportsValue
    Indicates that one entity provides justification, evidence, or backing for the truth, relevance, or appropriateness of a particular value associated with another entity.
  • C. supportsEvaluation
    Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to be assessed, tested, or evaluated.
  • D. supportsUse
    Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
  • E. supportsForm
    Indicates that one entity provides compatibility or backing for a particular form, format, or type 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_69c0085a1ed08190a7e9a8b6323fd680 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c048fc112c8190b905bf561c9de096 completed March 22, 2026, 7:54 p.m.
PD Predicate disambiguation batch_69c03352208c8190968efed05a9fd416 completed March 22, 2026, 6:22 p.m.
Created at: March 22, 2026, 4 p.m.