Triple
T15576077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flickr |
E374371
|
entity |
| Predicate | licenseOptions |
P119253
|
FINISHED |
| Object | all rights reserved |
—
|
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: all rights reserved | Statement: [Flickr, licenseOptions, all rights reserved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseOptions Context triple: [Flickr, licenseOptions, all rights reserved]
-
A.
licensePreference
Indicates a party’s chosen or prioritized type of license to use, grant, or operate under in a given context.
-
B.
licenseModel
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
-
C.
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.
-
D.
licenseScope
Indicates the specific rights, limitations, and conditions that define how and where a license may be used or applied.
-
E.
licenseFocus
Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
- F. None of above. chosen
Provenance (4 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e22c89081909b1ec0cd36a1ef45 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:10 a.m.