Triple
T22375493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MZLA Technologies Corporation |
E553141
|
entity |
| Predicate | softwareLicensingModel |
P8460
|
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: [MZLA Technologies Corporation, softwareLicensingModel, open source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareLicensingModel Context triple: [MZLA Technologies Corporation, softwareLicensingModel, open source]
-
A.
usesLicensingModel
Indicates that one entity employs or applies a particular licensing model in its operations or offerings.
-
B.
licenseModel
chosen
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
-
C.
typeOfLicensingItManaged
Indicates that one entity manages or oversees the licensing arrangements or permissions associated with another entity.
-
D.
engineLicenseBasedOn
Indicates that an engine’s license is determined or derived from another specified license or licensing basis.
-
E.
licenseFamily
Indicates that one license belongs to, is derived from, or is categorized under a broader family or class of related licenses.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15807cb748190abd9adc08ca1ad4f |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.