Triple

T35029785
Position Surface form Disambiguated ID Type / Status
Subject NonGNU ELPA E1010445 entity
Predicate relationToGNUELPA P206817 FINISHED
Object parallel archive for non-GNU-maintained packages 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: parallel archive for non-GNU-maintained packages | Statement: [NonGNU ELPA, relationToGNUELPA, parallel archive for non-GNU-maintained packages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relationToGNUELPA
Context triple: [NonGNU ELPA, relationToGNUELPA, parallel archive for non-GNU-maintained packages]
  • A. geneticRelation
    Indicates that two entities are connected through a hereditary or familial genetic relationship.
  • B. relationshipToRelative
    Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
  • C. relationToAncestors
    Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
  • D. relationToTheIndependent
    Indicates a relationship in which one entity is connected or relevant to another entity that is designated as independent.
  • E. governingRelation
    Indicates a relationship in which one entity exercises authority, control, or regulatory power over another.
  • 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_69f76dccf0108190af43b465d3750196 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a037c92f03c8190ae2751270b195423 completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a016960819093ed4990fb4d9d36 completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c82179081908325a59b8539b3a8 completed May 12, 2026, 7:16 p.m.
Created at: May 3, 2026, 4:01 p.m.