Triple

T3418926
Position Surface form Disambiguated ID Type / Status
Subject Apache License 1.1 E72071 entity
Predicate hasAttributionRequirement P20011 FINISHED
Object true 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: true | Statement: [Apache License 1.1, hasAttributionRequirement, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAttributionRequirement
Context triple: [Apache License 1.1, hasAttributionRequirement, true]
  • A. requiresAttribution chosen
    Indicates that one entity’s use, display, or distribution of another entity requires giving proper credit or acknowledgment to the original source.
  • B. hasTransparencyRequirement
    Indicates that one entity is obligated to provide clear, accessible information or disclosure to another entity or to the public.
  • C. hasEntryRequirement
    Indicates that one entity specifies conditions or qualifications that must be met before another entity is allowed access, participation, or admission.
  • D. hasMandate
    Indicates that an entity is officially authorized or required to perform a specific role, action, or set of responsibilities.
  • E. hasTicketRequirement
    Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
  • 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_69ad85ad38e48190b7660c5118a35289 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb92df1e48190bbf22a47e44579f1 completed March 8, 2026, 6 p.m.
PD Predicate disambiguation batch_69adadfcbc38819080852c18240451c5 completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:15 p.m.