Triple
T28596391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerrit (Wikimedia code review system) |
E723781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | code review system |
C19784
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: code review system Context triple: [Gerrit (Wikimedia code review system), instanceOf, code review system]
-
A.
open-source project hosting website
An open-source project hosting website is an online platform where developers can collaboratively store, manage, share, and track the development of publicly accessible software projects and their source code.
-
B.
bug tracking system
A bug tracking system is a software tool that records, organizes, and manages reported defects or issues throughout a product’s development and maintenance lifecycle.
-
C.
Git repository hosting service
A Git repository hosting service is an online platform that stores, manages, and facilitates collaboration on Git-based source code repositories, providing features like version control, access control, issue tracking, and integration with development tools.
-
D.
software development system
chosen
A software development system is an integrated environment of tools, processes, and infrastructure that supports the planning, creation, testing, deployment, and maintenance of software applications.
-
E.
SCM system
An SCM system (Supply Chain Management system) is a software platform that plans, executes, and monitors the end-to-end flow of goods, information, and finances across the supply chain to optimize efficiency, cost, and service levels.
- F. None of above.
Provenance (1 batch)
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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:22 a.m.