Triple

T7894358
Position Surface form Disambiguated ID Type / Status
Subject System V derivatives E183309 entity
Predicate licenseOrigin P79619 FINISHED
Object proprietary AT&T UNIX licenses 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: proprietary AT&T UNIX licenses | Statement: [System V derivatives, licenseOrigin, proprietary AT&T UNIX licenses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: licenseOrigin
Context triple: [System V derivatives, licenseOrigin, proprietary AT&T UNIX licenses]
  • A. licenseFocus
    Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
  • B. license
    Indicates that one entity has granted another entity formal permission or authorization to use, perform, or exploit something under specified terms.
  • C. licenseStatus
    Indicates the current state or condition of a license in relation to its validity, permissions, or compliance.
  • D. 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.
  • E. licenseBuiltIn
    Indicates that a license is inherently included within or comes standard as part of another product, service, or system rather than being added separately.
  • F. None of above. chosen

Provenance (4 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_69ca828c474c8190a254d6499871eaff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a15a7e88190a05474844817e5d2 completed March 31, 2026, 3:05 a.m.
PD Predicate disambiguation batch_69cae92d94448190b4425bbfb64c658c completed March 30, 2026, 9:20 p.m.
PDg Predicate description generation batch_69caf786ec748190b6347b0c94335550 completed March 30, 2026, 10:21 p.m.
Created at: March 30, 2026, 5:01 p.m.