Triple
T20165327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NES Zapper |
E491811
|
entity |
| Predicate | hasNoRumble |
P138918
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NES Zapper, hasNoRumble, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoRumble Context triple: [NES Zapper, hasNoRumble, true]
-
A.
hasHDVibration
Indicates that an entity provides or supports high-definition (precise, nuanced) vibration feedback in its interactions or operations.
-
B.
hasNoReflexesIn
Indicates that an entity lacks reflexive responses or reactions within a specified context, system, or body part.
-
C.
hasNoPowerOver
Indicates that one entity lacks authority, control, or influence over another entity or situation.
-
D.
hasNoisePerformance
Indicates the degree to which one entity’s operation or behavior produces or is characterized by a certain level or quality of noise.
-
E.
hasNoiseModes
Indicates that an entity supports or is associated with one or more distinct noise-related operating modes or settings.
- F. None of above. chosen
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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668442d2c81908bb1a0fac9895b5e |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:35 p.m.