Triple
T14334169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDW |
E355427
|
entity |
| Predicate | designDisciplines |
P62830
|
FINISHED |
| Object | product design |
—
|
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: product design | Statement: [DDW, designDisciplines, product design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designDisciplines Context triple: [DDW, designDisciplines, product design]
-
A.
designDiscipline
chosen
Indicates a relationship where an entity is associated with, categorized under, or practices a particular field or branch of design.
-
B.
designCategory
Indicates that one entity is classified under a particular design-related category or type.
-
C.
designSelectedIn
Indicates that a particular design has been chosen or picked out within a specific context, set, or selection process.
-
D.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
E.
designClass
Indicates that one entity is the design or blueprint class from which the other entity is derived or instantiated.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c20d2148190bb534bef338e871d |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.