Triple
T14415065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N91 |
E357427
|
entity |
| Predicate | musicPlaybackTime |
P102823
|
FINISHED |
| Object | up to 10 hours |
—
|
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: up to 10 hours | Statement: [Nokia N91, musicPlaybackTime, up to 10 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicPlaybackTime Context triple: [Nokia N91, musicPlaybackTime, up to 10 hours]
-
A.
musicPlaybackTimeClaimed
chosen
Indicates that a specific duration of music playback has been asserted or reported, typically as a claimed amount of listening or play time.
-
B.
continuityPosition
Indicates the relative ordering or placement of an element within a continuous sequence or flow of related elements.
-
C.
playedUntil
Indicates that an action or event involving playing continued up to a specific time, point, or condition.
-
D.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
-
E.
playerControl
Indicates that one entity (typically a player) has control or command over another entity or object within a system or environment.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90cc99208190a2313b1acfb5d802 |
completed | April 14, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:17 a.m.