Triple
T2795592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wietse Venema |
E53027
|
entity |
| Predicate | softwareLicensePreference |
P10960
|
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: [Wietse Venema, softwareLicensePreference, open source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareLicensePreference Context triple: [Wietse Venema, softwareLicensePreference, open source]
-
A.
licensePreference
chosen
Indicates a party’s chosen or prioritized type of license to use, grant, or operate under in a given context.
-
B.
licenseFamily
Indicates that one license belongs to, is derived from, or is categorized under a broader family or class of related licenses.
-
C.
requiresLicenseOf
Indicates that one entity must obtain or hold the license associated with another entity in order to use, access, or perform something.
-
D.
licenseFor
Indicates that one entity grants or holds formal permission or authorization for another entity to perform an activity, use a resource, or operate under specified conditions.
-
E.
licenseModel
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddef754081908e6218dc2208e0fd |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.