Triple
T31508496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tapestry Chambers |
E803879
|
entity |
| Predicate | hasFurnitureStyle |
P5509
|
FINISHED |
| Object | Rococo revival |
—
|
NE NERFINISHED |
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: Rococo revival | Statement: [Tapestry Chambers, hasFurnitureStyle, Rococo revival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFurnitureStyle Context triple: [Tapestry Chambers, hasFurnitureStyle, Rococo revival]
-
A.
usesHouseStyle
Indicates that one entity follows or applies the specific house style (a defined set of stylistic or formatting conventions) associated with another entity.
-
B.
interiorStyle
chosen
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
C.
furnishingType
Indicates the type or category of furnishings associated with an entity, such as a property or room.
-
D.
containsFurnitureBy
Indicates that one entity includes or holds furniture items that are provided, created, or specified by another entity.
-
E.
eraOfFurnishings
Indicates the historical time period or style from which a set of furnishings originates or to which it belongs.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 9:48 p.m.