Triple
T8302293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basque Wikinews |
E194375
|
entity |
| Predicate | hasCreativeCommonsLicense |
P9517
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Basque Wikinews, hasCreativeCommonsLicense, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreativeCommonsLicense Context triple: [Basque Wikinews, hasCreativeCommonsLicense, yes]
-
A.
hasCreativeCommonsLicensedWorks
chosen
Indicates that an entity possesses or is associated with works that are licensed under a Creative Commons license.
-
B.
canBeLicensedUnder
Indicates that something is eligible or suitable to be granted a particular legal license or licensing terms.
-
C.
hasDerivativeWork
Indicates that one work is based on, adapted from, or otherwise derived from another work.
-
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.
developedUnderLicenseFrom
Indicates that something was created or produced with formal permission granted through a licensing agreement from another party.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e8a45348190a7895b33abcb64c9 |
completed | March 31, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.