Triple
T14891263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iStockphoto |
E359757
|
entity |
| Predicate | licensingType |
P81697
|
FINISHED |
| Object | royalty-free |
—
|
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: royalty-free | Statement: [iStockphoto, licensingType, royalty-free]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licensingType Context triple: [iStockphoto, licensingType, royalty-free]
-
A.
licenseFamily
Indicates that one license belongs to, is derived from, or is categorized under a broader family or class of related licenses.
-
B.
licensingRestriction
chosen
Indicates that there is a constraint or condition imposed on the use, distribution, or modification of something under a specific license.
-
C.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
D.
licensingComponent
Indicates that one entity serves as a licensing-related component or module within the context or operation of another entity.
-
E.
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.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f883288190af602633fa7d6860 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 2:10 a.m.