Triple
T32062180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Licensing |
E818773
|
entity |
| Predicate | typeOfLicensingModel |
P50497
|
FINISHED |
| Object | patent pool |
—
|
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: patent pool | Statement: [Via Licensing, typeOfLicensingModel, patent pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLicensingModel Context triple: [Via Licensing, typeOfLicensingModel, patent pool]
-
A.
usesLicensingModel
chosen
Indicates that one entity employs or applies a particular licensing model in its operations or offerings.
-
B.
licenseModel
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.
licenseFamily
Indicates that one license belongs to, is derived from, or is categorized under a broader family or class of related licenses.
-
E.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00383e868c819098fd17e25fcbdb04 |
completed | May 10, 2026, 7:48 a.m. |
| PD | Predicate disambiguation | batch_6a0037cc59688190b7b9da939a413db3 |
completed | May 10, 2026, 7:46 a.m. |
Created at: May 1, 2026, 12:22 a.m.