Triple

T29404684
Position Surface form Disambiguated ID Type / Status
Subject GDK E745750 entity
Predicate stableReleaseBranchOf P31890 FINISHED
Object GTK 4 NE NERFINISHED

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: GTK 4 | Statement: [GDK, stableReleaseBranchOf, GTK 4]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: stableReleaseBranchOf
Context triple: [GDK, stableReleaseBranchOf, GTK 4]
  • A. latestReleaseBranch
    Indicates that a branch is designated as the most recent official release branch in a version control or release management system.
  • B. hasReleaseBranch chosen
    Indicates that an entity is associated with a specific release branch, typically representing a stabilized version line in a version control or release management system.
  • C. stableReleaseRepository
    Indicates that the referenced software artifact is stored in, or distributed through, a repository designated for stable (non-experimental) releases.
  • D. relatesToBranch
    Indicates a general association or connection between an entity and a specific branch (such as a subdivision, offshoot, or subunit) within a larger structure or system.
  • E. representedBranch
    Indicates that one entity serves as a representative or proxy for a particular branch of another entity or organization.
  • 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_69f0a79eb7d081908c67197a5f347e68 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f66a324ca48190b20c1f315ee9da9b completed May 2, 2026, 9:18 p.m.
PD Predicate disambiguation batch_69f66339175c819080bd70f0ff7057b1 completed May 2, 2026, 8:48 p.m.
Created at: April 28, 2026, 2:53 p.m.