Triple
T36359378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold Fusion |
E895444
|
entity |
| Predicate | releaseYearOfProduct |
P85605
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Cold Fusion, releaseYearOfProduct, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseYearOfProduct Context triple: [Cold Fusion, releaseYearOfProduct, 1994]
-
A.
yearAnnounced
Indicates the calendar year in which something (such as a product, event, or decision) was formally announced.
-
B.
deploymentYear
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
-
C.
releaseYearOfNotableVersion
Indicates the calendar year in which a notable or significant version of something was released.
-
D.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
E.
commercialReleaseYear
chosen
Indicates the calendar year in which a product, work, or item was first made commercially available to the public.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:09 p.m.