Triple
T36491796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | miniImageNet |
E899067
|
entity |
| Predicate | hasLicenseSource |
P198452
|
FINISHED |
| Object | ImageNet license |
—
|
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: ImageNet license | Statement: [miniImageNet, hasLicenseSource, ImageNet license]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLicenseSource Context triple: [miniImageNet, hasLicenseSource, ImageNet license]
-
A.
hasLicense
Indicates that an entity possesses a valid authorization or permit, typically granted by an authority, to perform a specific activity or use something.
-
B.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
C.
requiresLicenseFrom
Indicates that one entity must obtain formal permission or authorization from another entity before performing a specific activity or operation.
-
D.
hasLicenseCriteria
Indicates that an entity is subject to, or must satisfy, specific licensing requirements or conditions.
-
E.
supportsLicense
Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
| PDg | Predicate description generation | batch_69fee33485188190a43526c9d39e3b6a |
completed | May 9, 2026, 7:33 a.m. |
Created at: May 3, 2026, 4:10 p.m.