Triple
T17104604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barcelona Chair |
E415064
|
entity |
| Predicate | seatForm |
P125940
|
FINISHED |
| Object | rectangular cushion |
—
|
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: rectangular cushion | Statement: [Barcelona Chair, seatForm, rectangular cushion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatForm Context triple: [Barcelona Chair, seatForm, rectangular cushion]
-
A.
seatOn
Indicates that one entity is positioned or placed on a seat or seating surface associated with another entity.
-
B.
seatIs
Indicates that one entity functions as the seat or seating position of another entity.
-
C.
seatSince
Indicates that an entity has held a particular seat, position, or place continuously since a specified point in time.
-
D.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
-
E.
seatingPosition
Indicates the relative location or arrangement of an entity’s seat with respect to other seats or a reference point in a seating layout.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2591a881909c5f4f7db47f4d6c |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.