Triple

T36671643
Position Surface form Disambiguated ID Type / Status
Subject OpenEmbedded E905429 entity
Predicate supportsCustomDistributions P205004 FINISHED
Object yes 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: yes | Statement: [OpenEmbedded, supportsCustomDistributions, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsCustomDistributions
Context triple: [OpenEmbedded, supportsCustomDistributions, yes]
  • A. hasDistributions
    Indicates that an entity is associated with one or more distributions through which it is delivered, provided, or made available.
  • B. hasDistributionType
    Indicates the type or pattern of distribution associated with an entity, specifying how something is spread, allocated, or made available.
  • C. hasDistributionVariant
    Indicates that one entity is a variant or alternative form of another entity specifically in terms of its distribution characteristics or pattern.
  • D. allowsDistribution
    Indicates that one entity grants permission for another entity to distribute or disseminate something (e.g., content, products, or data).
  • E. supportsTimeDistribution
    Indicates that one entity provides or enables the allocation, scheduling, or distribution of time-related resources or events for another entity.
  • 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_69f76e6f10008190aea41746aa1b186e completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a037cad051c8190b28b354b89208574 completed May 12, 2026, 7:17 p.m.
PD Predicate disambiguation batch_6a037a0e039481908a4a2666f76c5363 completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c82f8c88190bd77a086023ac0e1 completed May 12, 2026, 7:16 p.m.
Created at: May 3, 2026, 4:12 p.m.