Triple
T29016671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin red |
E737326
|
entity |
| Predicate | primaryRoleInDesign |
P49737
|
FINISHED |
| Object | primary brand color |
—
|
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: primary brand color | Statement: [Virgin red, primaryRoleInDesign, primary brand color]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleInDesign Context triple: [Virgin red, primaryRoleInDesign, primary brand color]
-
A.
roleInDesignOf
Indicates that an entity participated in or held a specific function within the process of designing another entity.
-
B.
designerOccupation
Indicates that one entity serves as the professional designer or design specialist for another entity.
-
C.
designedRole
chosen
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to another entity.
-
D.
primaryDesignMedium
Indicates the main material, tool, or medium an entity primarily uses or is created in for its design or artistic expression.
-
E.
designerType
Indicates the specific kind or category of designer role associated with an entity.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a00a74c0564819081e1c4c29b9d0d15 |
completed | May 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_6a00a6a63ef48190a743c88534d9d672 |
completed | May 10, 2026, 3:39 p.m. |
Created at: April 28, 2026, 9:46 a.m.