Triple
T34541771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIMtrace |
E886823
|
entity |
| Predicate | hardwareLicense |
P147415
|
FINISHED |
| Object | open hardware license |
—
|
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 hardware license | Statement: [SIMtrace, hardwareLicense, open hardware license]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardwareLicense Context triple: [SIMtrace, hardwareLicense, open hardware license]
-
A.
licenceCode
Indicates that one entity is associated with a specific license identifier or code that governs its permitted use or distribution.
-
B.
licenseModel
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
-
C.
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.
-
D.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
E.
licenseOfProduct
chosen
Indicates that a specified license applies to, governs, or is associated with a particular product.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71ff6a6d48190b84bd9e1cc217e70 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.