Triple
T3418500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IntelliJ IDEA |
E72063
|
entity |
| Predicate | supportsVersionControl |
P9403
|
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: [IntelliJ IDEA, supportsVersionControl, Perforce]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Perforce Context triple: [IntelliJ IDEA, supportsVersionControl, 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.
Subversion
Subversion is a centralized version control system used to manage and track changes to source code and other files in software development projects.
-
C.
TFS
TFS is the IATA airport code for Tenerife South Airport, a major international gateway to Spain’s Canary Islands.
-
D.
Plastic SCM
Plastic SCM is a distributed version control system designed for large-scale and game development projects, offering advanced branching, merging, and graphical tools.
-
E.
Bitbucket
Bitbucket is a web-based platform for hosting Git repositories that provides source code management, collaboration tools, and integration with development workflows.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb92df1e48190bbf22a47e44579f1 |
completed | March 8, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b3546e710c8190a6b9523b77f6c893 |
completed | March 13, 2026, 12:03 a.m. |
Created at: March 8, 2026, 3:15 p.m.