Triple
T15174120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N95 |
E362560
|
entity |
| Predicate | supportsStereoFMRadio |
P116997
|
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, supportsStereoFMRadio, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStereoFMRadio Context triple: [Nokia N95, supportsStereoFMRadio, true]
-
A.
hasStereoOutput
Indicates that an entity provides or supports audio output in stereo (two-channel) format.
-
B.
hasNumberOfFMChannels
Indicates the relationship that specifies how many FM (frequency modulation) channels are associated with or supported by an entity.
-
C.
supportsStereoPairing
Indicates that an entity is capable of being paired with another similar entity to function together as a synchronized stereo audio system.
-
D.
hasRadio
Indicates that an entity is equipped with or includes a radio device.
-
E.
supportsAudioReturnChannel
Indicates that one entity is capable of handling an audio return channel from another entity, allowing audio to be sent back over the same connection.
- 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_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. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:09 a.m.