Triple
T8245322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neoprene |
E192836
|
entity |
| Predicate | commercializedInYear |
P40835
|
FINISHED |
| Object | 1931 |
—
|
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: 1931 | Statement: [Neoprene, commercializedInYear, 1931]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercializedInYear Context triple: [Neoprene, commercializedInYear, 1931]
-
A.
commercializedIn
Indicates that something has been brought to market or made available for commercial sale or use within a specified place or context.
-
B.
firstCommercialReleaseYear
chosen
Indicates the calendar year in which something (such as a product, work, or service) was first made commercially available to the public.
-
C.
brandLaunchYear
Indicates the calendar year in which a brand was first introduced or launched to the market.
-
D.
introducedInMarket
Indicates that an entity was first made available or launched for sale within a particular market or marketplace.
-
E.
onlineLaunchYear
Indicates the year in which something (such as a service, product, or website) was first launched or made available online.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7872f6d481909ea1d3c2aad1a2b1 |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.