Triple

T3547180
Position Surface form Disambiguated ID Type / Status
Subject Puma (licensed watches) E75023 entity
Predicate usesLicensingModel P50497 FINISHED
Object brand licensing agreement 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: brand licensing agreement | Statement: [Puma (licensed watches), usesLicensingModel, brand licensing agreement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesLicensingModel
Context triple: [Puma (licensed watches), usesLicensingModel, brand licensing agreement]
  • A. licenseModel
    Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
  • B. supportsLicense
    Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
  • C. requiresLicenseOf
    Indicates that one entity must obtain or hold the license associated with another entity in order to use, access, or perform something.
  • D. licenseEnforced
    Indicates that a license’s terms or restrictions are actively applied and upheld in relation to the associated entity or activity.
  • E. engineLicenseBasedOn
    Indicates that an engine’s license is determined or derived from another specified license or licensing basis.
  • 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_69ad85d33c6c819081d5ac1df13b5680 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbfcf64488190af8452308734028c completed March 8, 2026, 6:28 p.m.
PD Predicate disambiguation batch_69adb83270ac819083967db0570167d2 completed March 8, 2026, 5:56 p.m.
PDg Predicate description generation batch_69adba25c66c81909a05a97327828c41 completed March 8, 2026, 6:04 p.m.
Created at: March 8, 2026, 3:20 p.m.