Triple
T38478702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tempest 2000 |
E915610
|
entity |
| Predicate | notablePlatformReception |
P204677
|
FINISHED |
| Object | Atari Jaguar |
E267310
|
NE 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: Atari Jaguar | Statement: [Tempest 2000, notablePlatformReception, Atari Jaguar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlatformReception Context triple: [Tempest 2000, notablePlatformReception, Atari Jaguar]
-
A.
notableReception
Indicates that something has received significant attention, recognition, or response from audiences, critics, or the public.
-
B.
metacriticReception
Indicates the critical reception or review score an entity received on Metacritic.
-
C.
notableModelOnPlatform
Indicates that a particular model is recognized as notable or prominent on a given platform.
-
D.
notablePlatformStatus
Indicates that an entity holds a distinguished or officially recognized status on a particular platform.
-
E.
marketReception
Indicates how a product, service, or work is received, evaluated, and responded to by the market or audience after its introduction.
- F. None of above. chosen
Provenance (5 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a423f6f7e7c8190a655f8c77107d82a |
completed | June 29, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:31 p.m.