Triple
T13632631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandigarh low lounge chairs |
E325760
|
entity |
| Predicate | backrest |
P14113
|
FINISHED |
| Object | cane backrest |
—
|
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: cane backrest | Statement: [Chandigarh low lounge chairs, backrest, cane backrest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backrest Context triple: [Chandigarh low lounge chairs, backrest, cane backrest]
-
A.
hasBackrest
Indicates that one entity (typically a seat or seating object) includes or is equipped with a supporting backrest.
-
B.
hasBackrestType
chosen
Indicates the specific kind or style of backrest that an object (typically a seat or chair) possesses.
-
C.
backSupport
Indicates that one entity provides physical or structural support to the back of another entity.
-
D.
backing
Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
-
E.
seatRecline
Indicates that one entity adjusts or is capable of adjusting the backward tilt or reclining position of a seat relative to another entity or context.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.