Triple
T17104605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barcelona Chair |
E415064
|
entity |
| Predicate | backForm |
P125941
|
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, backForm, rectangular cushion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backForm Context triple: [Barcelona Chair, backForm, rectangular cushion]
-
A.
backType
Indicates the type or category of a backing or support associated with an entity.
-
B.
backing
Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
-
C.
backDescription
Indicates that an entity provides a description or textual information specifically about the back side or rear view of another entity.
-
D.
backsUp
Indicates that one entity provides support, reinforcement, or confirmation for another entity’s actions, statements, or position.
-
E.
exportForm
Indicates that one entity sends or transfers something (such as goods, data, or a document) out from its origin to another place, system, or jurisdiction in a specified format.
- 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.