Triple
T14362913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curriki |
E356148
|
entity |
| Predicate | contentLicenseType |
P23417
|
FINISHED |
| Object | open source |
—
|
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: open source | Statement: [Curriki, contentLicenseType, open source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentLicenseType Context triple: [Curriki, contentLicenseType, open source]
-
A.
contentLicense
chosen
Indicates the type of license or usage rights that govern how the associated content may be used, shared, or redistributed.
-
B.
contentLicenseAllows
Indicates that a content license grants permission for a specified use or action involving the content.
-
C.
contentLicenseRequires
Indicates that the terms of a content’s license obligate certain conditions, actions, or permissions to be met or granted when using that content.
-
D.
licensingRestriction
Indicates that there is a constraint or condition imposed on the use, distribution, or modification of something under a specific license.
-
E.
licensingBasisIncludes
Indicates that one licensing basis incorporates or contains another licensing basis as part of its governing conditions or requirements.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fabec088190bd8128371b29e958 |
completed | April 14, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:15 a.m.