Triple
T36955814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jet Force Gemini |
E914184
|
entity |
| Predicate | supportsControllerFeature |
P203
|
FINISHED |
| Object | Nintendo 64 Rumble Pak |
E1156370
|
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: Nintendo 64 Rumble Pak | Statement: [Jet Force Gemini, supportsControllerFeature, Nintendo 64 Rumble Pak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsControllerFeature Context triple: [Jet Force Gemini, supportsControllerFeature, Nintendo 64 Rumble Pak]
-
A.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
supportsControllerInput
Indicates that an entity is capable of receiving and handling input from a controller device.
-
C.
supportsBusController
Indicates that one entity provides the necessary functionality or compatibility to operate, manage, or interface with a bus controller for another entity.
-
D.
supportsSoftwareControl
Indicates that one entity enables or is compatible with the management, operation, or regulation of another entity through software-based control mechanisms.
-
E.
supportsAt
Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
- F. None of above.
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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c3a73788190ab9079adfc537786 |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.