Triple
T10475307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Deréon |
E247029
|
entity |
| Predicate | designElements |
P29429
|
FINISHED |
| Object | embellished details |
—
|
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: embellished details | Statement: [House of Deréon, designElements, embellished details]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designElements Context triple: [House of Deréon, designElements, embellished details]
-
A.
visualElements
chosen
Indicates that one entity contains, uses, or is characterized by specific visual components or graphical features associated with another entity.
-
B.
urbanDesignElement
Indicates a relationship where something functions as a designed feature or component that shapes the form, use, or experience of an urban environment.
-
C.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
D.
designSelectedIn
Indicates that a particular design has been chosen or picked out within a specific context, set, or selection process.
-
E.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5094f6b408190a5a26b1a82e4a02b |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:21 p.m.