Triple
T18050469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Source Initiative |
E431914
|
entity |
| Predicate | licenseListType |
P129617
|
FINISHED |
| Object | OSI-approved licenses |
—
|
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: OSI-approved licenses | Statement: [Open Source Initiative, licenseListType, OSI-approved licenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseListType Context triple: [Open Source Initiative, licenseListType, OSI-approved licenses]
-
A.
licenseListIncludes
Indicates that a specified license list contains or covers a particular license or licensing term.
-
B.
licenseFamily
Indicates that one license belongs to, is derived from, or is categorized under a broader family or class of related licenses.
-
C.
licenseFocus
Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
-
D.
licenseOptions
Indicates the available licensing choices or configurations that can be applied to an entity or resource.
-
E.
licenseName
Indicates the specific name or title of the license under which an entity is provided or governed.
- F. None of above. chosen
Provenance (4 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff57ea08190a30a87993f7d3299 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:25 a.m.