Triple
T8610484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rust-VMM project |
E203902
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open source software project |
C2951
|
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: open source software project Context triple: [Rust-VMM project, instanceOf, open source software project]
-
A.
free software project
chosen
A free software project is a collaboratively developed software initiative whose source code is openly available and may be used, modified, and redistributed under a license that guarantees these freedoms.
-
B.
open-source organization
An open-source organization is a collaborative entity that develops, maintains, and governs software or other projects whose source materials are publicly accessible, modifiable, and distributable under open licenses.
-
C.
open source software interface
An open source software interface is a publicly accessible set of interaction points, such as APIs or user interfaces, whose underlying code is openly available for use, modification, and distribution under an open source license.
-
D.
open source contributor
An open source contributor is an individual who voluntarily improves, maintains, or supports publicly available software or documentation by submitting code, reporting issues, reviewing changes, or providing other collaborative input.
-
E.
open-source software advocate
An open-source software advocate is a person who actively promotes the use, development, and principles of open-source software, emphasizing transparency, collaboration, and community-driven innovation.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:25 p.m.