Triple

T29873791
Position Surface form Disambiguated ID Type / Status
Subject NGINX, Inc. E758663 entity
Predicate softwareLicenseForCoreProduct P147415 FINISHED
Object 2‑clause BSD license 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: 2‑clause BSD license | Statement: [NGINX, Inc., softwareLicenseForCoreProduct, 2‑clause BSD license]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: softwareLicenseForCoreProduct
Context triple: [NGINX, Inc., softwareLicenseForCoreProduct, 2‑clause BSD license]
  • A. licenseOfProduct chosen
    Indicates that a specified license applies to, governs, or is associated with a particular product.
  • B. softwareLicenseWorkedWith
    Indicates that a particular software license has been used or handled in the course of working with a given software product, project, or component.
  • C. licenseFor
    Indicates that one entity grants or holds formal permission or authorization for another entity to perform an activity, use a resource, or operate under specified conditions.
  • D. licenseModel
    Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
  • E. licenseFamily
    Indicates that one license belongs to, is derived from, or is categorized under a broader family or class of related licenses.
  • 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_69f2245d0d7081909e37ee328542bcd7 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f676f968d08190a4adba0439b438c9 completed May 2, 2026, 10:13 p.m.
PD Predicate disambiguation batch_69f675ff62c48190a634bbb8896973b9 completed May 2, 2026, 10:09 p.m.
Created at: April 29, 2026, 5:54 p.m.