Triple
T10450863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo DSi Browser |
E246417
|
entity |
| Predicate | hardwareIntegration |
P33720
|
FINISHED |
| Object | dual screens of Nintendo DSi |
—
|
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: dual screens of Nintendo DSi | Statement: [Nintendo DSi Browser, hardwareIntegration, dual screens of Nintendo DSi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardwareIntegration Context triple: [Nintendo DSi Browser, hardwareIntegration, dual screens of Nintendo DSi]
-
A.
hardwareComponent
Indicates that one entity is a physical hardware part or module that is contained in, attached to, or functionally part of another hardware system or device.
-
B.
hardwareRole
Indicates the functional role or purpose that a piece of hardware serves within a system or configuration.
-
C.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
D.
hardwareIncluded
chosen
Indicates that certain hardware components are provided or come bundled together with another item or product.
-
E.
hardwarePlatformFor
Indicates that one entity serves as the hardware platform on which another entity is designed to run or be deployed.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe0a6a548190a54212912f618e4e |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:17 p.m.