Triple

T7937202
Position Surface form Disambiguated ID Type / Status
Subject Subversion E184313 entity
Predicate competesWith P1375 FINISHED
Object Perforce E183366 NE 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: Perforce | Statement: [Subversion, competesWith, Perforce]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Perforce
Context triple: [Subversion, competesWith, Perforce]
  • A. Perforce chosen
    Perforce is a centralized version control system widely used in game development and large-scale software projects for its performance and robust asset management.
  • B. CollabNet
    CollabNet is a software development and DevOps company best known for creating and stewarding the Subversion (SVN) version control system.
  • C. Concurrent Versions System
    Concurrent Versions System (CVS) is an early, widely used open-source version control system that manages changes to source code in collaborative software development.
  • D. Subversion
    Subversion is a centralized version control system used to manage and track changes to source code and other files in software development projects.
  • E. TFS
    TFS is the IATA airport code for Tenerife South Airport, a major international gateway to Spain’s Canary Islands.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca8290c21c8190906a5ca6fe2b03c4 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3aef2394819086eea1f6ab117aed completed March 31, 2026, 3:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbe019a094819082baecdcb007c84f completed March 31, 2026, 2:54 p.m.
Created at: March 30, 2026, 5:08 p.m.