Triple
T3603933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Womb chair for Knoll |
E76324
|
entity |
| Predicate | introducedToMarketInYear |
P3297
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [Womb chair for Knoll, introducedToMarketInYear, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedToMarketInYear Context triple: [Womb chair for Knoll, introducedToMarketInYear, 1948]
-
A.
introducedInMarket
Indicates that an entity was first made available or launched for sale within a particular market or marketplace.
-
B.
introducedInYear
chosen
Indicates the year in which something was first introduced, launched, or made available.
-
C.
regulatoryApprovalYear
Indicates the calendar year in which an official regulatory body granted approval for the referenced item, action, or entity.
-
D.
formulatedInYear
Indicates the specific calendar year in which something was originally created, devised, or formally established.
-
E.
deploymentYear
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1e07bc481908d9fce18d36d8e0d |
completed | March 8, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.