Triple
T8671272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wassily Chair |
E205801
|
entity |
| Predicate | backSupport |
P84000
|
FINISHED |
| Object | strapped leather |
—
|
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: strapped leather | Statement: [Wassily Chair, backSupport, strapped leather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backSupport Context triple: [Wassily Chair, backSupport, strapped leather]
-
A.
backing
Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
-
B.
backedFor
Indicates that one entity provides support, endorsement, or backing for another entity, often in a financial, political, or strategic context.
-
C.
supportingBody
Indicates that one entity serves as a supporting or backing body for another entity, providing endorsement, resources, or structural support.
-
D.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
E.
supportStyle
Indicates the manner or approach by which one entity provides assistance or backing to another.
- F. None of above. chosen
Provenance (4 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4918e3a88190b3c49043211840fd |
completed | March 31, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:31 p.m.