Triple
T28421744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian contrib component |
E719956
|
entity |
| Predicate | softwareLicenseStatus |
P48284
|
FINISHED |
| Object | free software |
—
|
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: free software | Statement: [Debian contrib component, softwareLicenseStatus, free software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareLicenseStatus Context triple: [Debian contrib component, softwareLicenseStatus, free software]
-
A.
licenseStatus
chosen
Indicates the current state or condition of a license in relation to its validity, permissions, or compliance.
-
B.
licenseUsed
Indicates that a particular license has been applied to or is being utilized for a specific resource, activity, or entity.
-
C.
licenseStewardship
Indicates that one entity is responsible for managing, overseeing, or administering a license on behalf of another entity.
-
D.
softwareLicensingAdvocacy
Indicates advocacy efforts aimed at promoting, defending, or influencing policies and practices related to software licensing.
-
E.
licenseModel
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 1:34 a.m.