Triple

T14439600
Position Surface form Disambiguated ID Type / Status
Subject Apache Ant E358051 entity
Predicate stableReleaseRepository P114281 FINISHED
Object Apache Ant download page 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: Apache Ant download page | Statement: [Apache Ant, stableReleaseRepository, Apache Ant download page]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: stableReleaseRepository
Context triple: [Apache Ant, stableReleaseRepository, Apache Ant download page]
  • A. stableReleaseStatus
    Indicates the release status or condition of a stable version of something (such as software or a product).
  • B. stableReleaseInput
    Indicates that an entity serves as the input or basis for determining a stable (official) release version of another entity.
  • C. stableReleasesMaintainedBy
    Indicates that the stable (non-development) releases of a software project are currently being maintained or supported by a particular entity.
  • D. supportsReleasesOf
    Indicates that one entity provides assistance, resources, or endorsement for the publication or rollout of another entity’s releases.
  • E. stableReleaseNaming
    Indicates that a software project’s stable release is identified or labeled using a particular naming convention.
  • 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_69d8279402a88190821ffa39ae15bccf completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de914c1398819090fa2a74d257ba3e completed April 14, 2026, 7:11 p.m.
PD Predicate disambiguation batch_69de5c3a02fc819097373f97a260cdeb completed April 14, 2026, 3:24 p.m.
PDg Predicate description generation batch_69de5fb4de14819092acdecbd201d672 completed April 14, 2026, 3:39 p.m.
Created at: April 10, 2026, 1:18 a.m.