Triple
T9897393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Office Home and Student 2013 RT |
E182209
|
entity |
| Predicate | licenseRestriction |
P81697
|
FINISHED |
| Object | non-commercial use |
—
|
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: non-commercial use | Statement: [Microsoft Office Home and Student 2013 RT, licenseRestriction, non-commercial use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseRestriction Context triple: [Microsoft Office Home and Student 2013 RT, licenseRestriction, non-commercial use]
-
A.
licensingRestriction
chosen
Indicates that there is a constraint or condition imposed on the use, distribution, or modification of something under a specific license.
-
B.
licenseConcern
Indicates that there is an issue, risk, or consideration related to a license associated with the entities involved.
-
C.
license
Indicates that one entity has granted another entity formal permission or authorization to use, perform, or exploit something under specified terms.
-
D.
licenseScope
Indicates the specific rights, limitations, and conditions that define how and where a license may be used or applied.
-
E.
licenseStatus
Indicates the current state or condition of a license in relation to its validity, permissions, or compliance.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4ab15f881909f75a8e01051dbc4 |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.