Triple

T8610120
Position Surface form Disambiguated ID Type / Status
Subject Gentoo ebuild repository E203894 entity
Predicate contributedToBy P30146 FINISHED
Object Gentoo community 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: Gentoo community | Statement: [Gentoo ebuild repository, contributedToBy, Gentoo community]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: contributedToBy
Context triple: [Gentoo ebuild repository, contributedToBy, Gentoo community]
  • A. hasContributionFrom chosen
    Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
  • B. tributeTo
    Indicates that one entity is created, given, or dedicated as a mark of respect, admiration, or honor toward another entity.
  • C. tributeFrom
    Indicates that one entity pays or provides tribute, often as a sign of submission or obligation, to another entity.
  • D. creditedFor
    Indicates that one entity is acknowledged as the source, contributor, or originator responsible for another entity (such as a work, achievement, or outcome).
  • E. contributeTo
    Indicates that one entity provides support, resources, or effort that helps bring about, enhance, or maintain another entity, outcome, or state.
  • 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_69ca832c23e4819095a9f3eea4a21828 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc46ee96ac8190809817c403da2889 completed March 31, 2026, 10:13 p.m.
PD Predicate disambiguation batch_69cc455437488190b7506f820daf6e32 completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:25 p.m.