Triple

T4443373
Position Surface form Disambiguated ID Type / Status
Subject Random E96222 entity
Predicate supportsDistribution P10379 FINISHED
Object uniform distribution 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: uniform distribution | Statement: [Random, supportsDistribution, uniform distribution]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsDistribution
Context triple: [Random, supportsDistribution, uniform distribution]
  • A. allowsDistribution
    Indicates that one entity grants permission for another entity to distribute or disseminate something (e.g., content, products, or data).
  • B. hasDistributions chosen
    Indicates that an entity is associated with one or more distributions through which it is delivered, provided, or made available.
  • C. supportedIn
    Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
  • D. supportedAs
    Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
  • E. distributesIn
    Indicates that one entity allocates or hands out something (e.g., items, resources, information) within or across a specified area, group, or context.
  • 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_69b345415ba481908df738e7174448ba completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b355b052688190a0d8e5912f82151c completed March 13, 2026, 12:09 a.m.
PD Predicate disambiguation batch_69b34f62c180819097ced38da2052207 completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:32 p.m.