Triple
T10827811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FreedomBox |
E255538
|
entity |
| Predicate | softwareLicenseVersion |
P8460
|
FINISHED |
| Object | GPLv3 or later |
—
|
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: GPLv3 or later | Statement: [FreedomBox, softwareLicenseVersion, GPLv3 or later]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareLicenseVersion Context triple: [FreedomBox, softwareLicenseVersion, GPLv3 or later]
-
A.
softwareLicenseWorkedWith
Indicates that a particular software license has been used or handled in the course of working with a given software product, project, or component.
-
B.
supportsLicense
Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
-
C.
licenseBuiltAs
Indicates that one entity is constructed, configured, or deployed under the terms or identity of another entity’s license.
-
D.
licenseModel
chosen
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
-
E.
softwareName
Indicates that one entity is the name or title of a software application associated with another entity.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d2b9f88190b79a7b168d7836c8 |
completed | April 9, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.