Triple
T26809906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violet Eyes |
E671958
|
entity |
| Predicate | hasLicensee |
P15136
|
FINISHED |
| Object | Elizabeth Arden |
—
|
NE NERFINISHED |
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: Elizabeth Arden | Statement: [Violet Eyes, hasLicensee, Elizabeth Arden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLicensee Context triple: [Violet Eyes, hasLicensee, Elizabeth Arden]
-
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.
hasLicenseCriteria
Indicates that an entity is subject to, or must satisfy, specific licensing requirements or conditions.
-
D.
licensee
chosen
Indicates that one entity is authorized by another, through a license agreement, to use or exploit certain rights, property, or resources.
-
E.
ownsLicensesUnderBrand
Indicates that one entity holds or possesses licenses that are issued under, associated with, or governed by a particular brand.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 4:28 a.m.