Triple
T28682330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kleenex |
E726038
|
entity |
| Predicate | brandNameForm |
P124579
|
FINISHED |
| Object | portmanteau |
—
|
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: portmanteau | Statement: [Kleenex, brandNameForm, portmanteau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandNameForm Context triple: [Kleenex, brandNameForm, portmanteau]
-
A.
brandNameType
chosen
Indicates the specific type or category associated with a brand name within a broader branding or naming system.
-
B.
brandNameUsedIn
Indicates that a particular brand name is used or appears within a specified context, such as a product, document, or communication.
-
C.
formedBrand
Indicates that an entity created or established a particular brand as a distinct commercial or organizational identity.
-
D.
brandNameVariant
Indicates that one brand name is an alternative or variant form of another brand name, such as a spelling, regional, or stylistic variation.
-
E.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 5:10 a.m.