Triple

T28627386
Position Surface form Disambiguated ID Type / Status
Subject Wikidata development team E724559 entity
Predicate usesSoftwareDevelopmentMethodology P41845 FINISHED
Object agile software development 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: agile software development | Statement: [Wikidata development team, usesSoftwareDevelopmentMethodology, agile software development]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesSoftwareDevelopmentMethodology
Context triple: [Wikidata development team, usesSoftwareDevelopmentMethodology, agile software development]
  • A. developedMethodology
    Indicates that one entity created, designed, or established a specific methodology used by another entity or in a particular context.
  • B. hasMethodologyFeature
    Indicates that something possesses or is characterized by a particular methodological attribute, technique, or feature.
  • C. developmentMethod chosen
    Indicates the process, technique, or approach used to create, build, or evolve something.
  • D. usesSoftwareModel
    Indicates that one entity employs or relies on a particular software model to perform its functions or tasks.
  • E. developmentProcessIncludes
    Indicates that a particular activity, phase, or component is part of, or contained within, a broader development process.
  • 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_69f01d822ac08190932de59ec2268ed2 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f739a638748190808e7a2930dce16e completed May 3, 2026, 12:03 p.m.
PD Predicate disambiguation batch_69f732f2dc6c8190a4e86da98cc5eb05 completed May 3, 2026, 11:35 a.m.
Created at: April 28, 2026, 4:36 a.m.