Triple
T492179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LC2 armchair |
E10211
|
entity |
| Predicate | hasCushionArrangement |
P2362
|
FINISHED |
| Object | separate seat, back, and side cushions |
—
|
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: separate seat, back, and side cushions | Statement: [LC2 armchair, hasCushionArrangement, separate seat, back, and side cushions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCushionArrangement Context triple: [LC2 armchair, hasCushionArrangement, separate seat, back, and side cushions]
-
A.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
B.
chairType
Indicates the specific kind or category of chair that an entity is classified as.
-
C.
hasSeat
Indicates that one entity possesses, provides, or includes a seat for another entity.
-
D.
furnishingType
Indicates the type or category of furnishings associated with an entity, such as a property or room.
-
E.
arrangement
chosen
Indicates a relationship where entities are organized, ordered, or positioned in a particular configuration or sequence relative to one another.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f0f959b481908f9f28fb96695924 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf7ce008190836fb6ab5ea39375 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.