Triple
T32023114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aino Aalto glassware series |
E817746
|
entity |
| Predicate | firstDesigned |
P206147
|
FINISHED |
| Object | 1932 |
—
|
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: 1932 | Statement: [Aino Aalto glassware series, firstDesigned, 1932]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDesigned Context triple: [Aino Aalto glassware series, firstDesigned, 1932]
-
A.
firstDeveloped
Indicates that one entity was the earliest to create, originate, or bring another entity into existence.
-
B.
wasFirstProducedBy
Indicates that something (such as a product, work, or item) was initially created, manufactured, or brought into existence by a particular agent, organization, or producer.
-
C.
firstDeployedIn
Indicates the time or place where something (such as a system, product, or technology) was initially put into operational use or service.
-
D.
wasFirstCommercializedBy
Indicates that the subject was initially brought to market or made commercially available by the object.
-
E.
firstPrototypeYear
Indicates the year in which the first prototype of an entity was created or completed.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:17 a.m.