Triple
T2751454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | i.am+ |
E60995
|
entity |
| Predicate | hasBrandIdentity |
P11989
|
FINISHED |
| Object | fashion-oriented technology |
—
|
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: fashion-oriented technology | Statement: [i.am+, hasBrandIdentity, fashion-oriented technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandIdentity Context triple: [i.am+, hasBrandIdentity, fashion-oriented technology]
-
A.
hasBranding
chosen
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
B.
hasGlobalBrand
Indicates that an entity possesses a brand that is recognized and operates across multiple countries or worldwide.
-
C.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
-
D.
hasUnderlyingCompanyBrand
Indicates that one entity is associated with or operates under the corporate brand of another company as its underlying brand.
-
E.
brandingStatus
Indicates the current state or condition of an entity’s branding, such as whether its brand identity has been defined, applied, updated, or is pending.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb6b6f0c8190901ab032dfb21e37 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.