Triple

T2113787
Position Surface form Disambiguated ID Type / Status
Subject MIT License E42560 entity
Predicate hasNoRequirement P6844 FINISHED
Object to disclose source code 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: to disclose source code | Statement: [MIT License, hasNoRequirement, to disclose source code]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNoRequirement
Context triple: [MIT License, hasNoRequirement, to disclose source code]
  • A. isNotRequiredFor chosen
    Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
  • B. dialogRequirement
    Indicates that a certain condition, piece of information, or interaction must occur within a dialog or conversation for a related action, state, or process to proceed or be considered valid.
  • C. doesNotHave
    Indicates that one entity lacks, is missing, or is not in possession of another entity or attribute.
  • D. evaluationRequirement
    Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
  • E. hasConformanceRequirements
    Indicates that an entity is subject to specific rules, standards, or criteria that it must satisfy or comply with.
  • 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_69a8871040f08190aac2e2d0ab6b47ad completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abbb05b51c81908a78c816f492c45c completed March 7, 2026, 5:43 a.m.
PD Predicate disambiguation batch_69abb7ba08948190a3c236bb53ee4257 completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:43 p.m.