Triple
T33890269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Lyle Williams |
E868739
|
entity |
| Predicate | associatedWithBrandCreation |
P206722
|
FINISHED |
| Object | Maybelline |
E28311
|
NE 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: Maybelline | Statement: [Thomas Lyle Williams, associatedWithBrandCreation, Maybelline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBrandCreation Context triple: [Thomas Lyle Williams, associatedWithBrandCreation, Maybelline]
-
A.
hasBrandCreated
Indicates that a particular brand is responsible for creating or producing a given entity.
-
B.
connectedToBrand
Indicates that one entity has an association or linkage with a particular brand, such as affiliation, representation, or integration.
-
C.
associatedWithBrandValues
Indicates that one entity is connected or aligned with the brand values, principles, or identity represented by another entity.
-
D.
associatedBrandCategory
Indicates that a brand is linked to or classified under a particular product or service category.
-
E.
associatedWithCityBranding
Indicates a relationship where something is connected to, involved in, or contributes to the branding or promotional identity of a city.
- F. None of above. chosen
Provenance (5 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3692c8b69c8190b3fb2556882232b8 |
completed | June 20, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.