Triple
T32062166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Licensing |
E818773
|
entity |
| Predicate | offeredLicensesTo |
P193727
|
FINISHED |
| Object | device manufacturers |
—
|
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: device manufacturers | Statement: [Via Licensing, offeredLicensesTo, device manufacturers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredLicensesTo Context triple: [Via Licensing, offeredLicensesTo, device manufacturers]
-
A.
offeredLicensesFor
chosen
Indicates that one party has presented or made available specific licenses to another party for consideration or acceptance.
-
B.
offersLicense
Indicates that one entity grants or makes available a license to another entity.
-
C.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
D.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
E.
offersInterface
Indicates that one entity provides or exposes a specific interface that another entity can use or interact with.
- 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_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 1, 2026, 12:22 a.m.