Triple
T22447146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artistic-2.0 |
E554889
|
entity |
| Predicate | isFSFLibre |
P34111
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Artistic-2.0, isFSFLibre, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFSFLibre Context triple: [Artistic-2.0, isFSFLibre, true]
-
A.
FSFApproved
Indicates that something has been reviewed and approved by the Free Software Foundation as meeting its free software licensing criteria.
-
B.
softwareFreedomStatus
chosen
Indicates the degree to which a piece of software respects users’ freedoms to use, study, modify, and share it.
-
C.
isGPLCompatible
Indicates that a software license is legally compatible with the GNU General Public License (GPL), allowing code to be combined and distributed under GPL terms.
-
D.
isCopyleft
Indicates that the subject is governed by a copyleft license, requiring derivative works to be distributed under the same or compatible licensing terms.
-
E.
openSourceStatus
Indicates whether something is publicly available under an open-source license, allowing use, modification, and distribution of its source.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b48be0481909f4601b732424e5b |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.