Triple

T11656854
Position Surface form Disambiguated ID Type / Status
Subject Joltid E277030 entity
Predicate providedLicensingFor P12718 FINISHED
Object Skype core P2P technology 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: Skype core P2P technology | Statement: [Joltid, providedLicensingFor, Skype core P2P technology]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: providedLicensingFor
Context triple: [Joltid, providedLicensingFor, Skype core P2P technology]
  • A. hasLicensing
    Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
  • B. licenseFor chosen
    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.
  • C. licensingComponent
    Indicates that one entity serves as a licensing-related component or module within the context or operation of another entity.
  • D. supportsLicense
    Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
  • E. licensingBasisIncludes
    Indicates that one licensing basis incorporates or contains another licensing basis as part of its governing conditions or requirements.
  • 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_69d6aafbb3c081908a9cdb4ecb8d981d completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a3d0331481909682b2e504e4c9a0 completed April 10, 2026, 7:16 a.m.
PD Predicate disambiguation batch_69d85ddc780481909a3bc63832fe2bd2 completed April 10, 2026, 2:18 a.m.
Created at: April 8, 2026, 9:39 p.m.