Triple
T6721938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab Room |
E153416
|
entity |
| Predicate | interiorDesignType |
P5509
|
FINISHED |
| Object | Middle Eastern–inspired interior |
—
|
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: Middle Eastern–inspired interior | Statement: [Arab Room, interiorDesignType, Middle Eastern–inspired interior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interiorDesignType Context triple: [Arab Room, interiorDesignType, Middle Eastern–inspired interior]
-
A.
interiorStyle
chosen
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
B.
furnishingType
Indicates the type or category of furnishings associated with an entity, such as a property or room.
-
C.
designCategory
Indicates that one entity is classified under a particular design-related category or type.
-
D.
designIntent
Indicates the underlying purpose, rationale, or functional goal that guided the creation or configuration of something.
-
E.
decorativeCategory
Indicates that one entity is classified as belonging to a particular decorative style, theme, or ornamentation category of another 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d139d50c81908b19120f139deaa5 |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:08 p.m.