Triple
T10450864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo DSi Browser |
E246417
|
entity |
| Predicate | topScreenUsage |
P94105
|
FINISHED |
| Object | page overview |
—
|
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: page overview | Statement: [Nintendo DSi Browser, topScreenUsage, page overview]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topScreenUsage Context triple: [Nintendo DSi Browser, topScreenUsage, page overview]
-
A.
platformUsage
Indicates how an entity uses, engages with, or relies on a particular platform for its activities or services.
-
B.
screenTimeFocus
Indicates the amount or proportion of time an entity’s attention or activity is concentrated on a particular screen or digital display.
-
C.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
D.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
E.
hasScreenTimeIn
Indicates that an entity appears on screen for a certain duration within a specified audiovisual work or segment.
- 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_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. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:17 p.m.