Triple
T16530001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ThrustSSC |
E401537
|
entity |
| Predicate | predecessor |
P97
|
FINISHED |
| Object | Thrust2 |
E401536
|
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: Thrust2 | Statement: [ThrustSSC, predecessor, Thrust2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thrust2 Context triple: [ThrustSSC, predecessor, Thrust2]
-
A.
Thrust2
chosen
Thrust2 is a British jet-powered car that set the world land speed record in 1983, driven by Richard Noble.
-
B.
Thrust
Thrust is a C++ template library for CUDA that provides high-level parallel algorithms and data structures to simplify GPU programming.
-
C.
Tempest Engine
Tempest Engine is Sony’s dedicated 3D audio processing hardware used in the PlayStation 5 to deliver immersive, spatial sound in games.
-
D.
PhysX
PhysX is a real-time physics simulation engine developed by NVIDIA, widely used in games and interactive applications to model realistic physical behavior.
-
E.
Aurora Engine
Aurora Engine is a role-playing game engine developed by BioWare, best known for powering classic titles like Neverwinter Nights.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed625208190a68b879266b05b3f |
completed | April 18, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0067a913388190afebe40fcc42e731 |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:14 a.m.