Triple
T15174121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N95 |
E362560
|
entity |
| Predicate | supportsMP3Playback |
P100240
|
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: [Nokia N95, supportsMP3Playback, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMP3Playback Context triple: [Nokia N95, supportsMP3Playback, true]
-
A.
supportsMusicPlayer
chosen
Indicates that one entity provides compatibility with or functionality for operating a music player associated with another entity.
-
B.
supportsPCM
Indicates that one entity is capable of handling, processing, or is compatible with PCM (Pulse-Code Modulation) audio data used by another entity.
-
C.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
D.
hasPlayFormat
Indicates that something (such as a game, media, or activity) is associated with a particular format or mode in which it is played or experienced.
-
E.
supportsVideoPlayback
Indicates that an entity is capable of playing or rendering video content.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006501b488190a2ab09dbf1532571 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.