Triple
T11060111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QGIS |
E261485
|
entity |
| Predicate | openSourceModel |
P25429
|
FINISHED |
| Object | community-driven development |
—
|
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: community-driven development | Statement: [QGIS, openSourceModel, community-driven development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openSourceModel Context triple: [QGIS, openSourceModel, community-driven development]
-
A.
coPilotWith
Indicates that two entities jointly serve as pilots or share piloting responsibilities for the same vehicle or mission.
-
B.
coPilotOf
Indicates that one entity serves as the co-pilot assisting and supporting another entity in operating or navigating a vehicle or craft.
-
C.
openSourceProject
chosen
Indicates that the subject is a software project whose source code is publicly available and can be used, modified, and redistributed under an open-source license.
-
D.
hasLanguageModel
Indicates that an entity possesses, uses, or is associated with a particular language model.
-
E.
openSource
Indicates that the subject makes its source code publicly available under a license that allows others to use, modify, and redistribute it.
- F. None of above.
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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798e991848190b07c2f48dae38681 |
completed | April 9, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.